headers
Lars Stokholm | 1 Apr 2005 22:56
Picon

Re: [Win32] Ctrl-G doesn't abort download of headers

Lars Stokholm wrote:

> I was afraid of that. I don't know where to start looking, and even if I found
> something I'd have no idea what to do with it. I'm not lazy, just not capable.

I'm sorry for replying to myself, but I found this:
http://www.s-lang.org/doc/html/cslang-4.html#ss4.1

So I thought I'd try and change 7 to 34 in slrn's init_tty, but it didn't work:

   if (-1 == SLang_init_tty (34, !Slrn_Use_Flow_Control, 0))
     slrn_exit_error (_("Unable to initialize the tty"));

That's about as far as I can get. Any ideas? Maybe Windows is not an
MSDOS system? Perhaps I need another scan code? How can I see
what Ctrl-G returns?

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 0 comments |
headers
Jurriaan | 1 Apr 2005 19:38
Picon
Picon
Favicon

Re: [Win32] Ctrl-G doesn't abort download of headers

From: Lars Stokholm <lars.stokholm <at> gmail.com>
Date: Thu, Mar 31, 2005 at 08:37:47PM +0200
> Jurriaan on adsl-gate wrote:
> 
> > The way to solve this is to find another program compiled like slrn, and
> > check their source to see how this is handled. Is there a version of
> > Mutt for win32, for example?
> 
> Well there's http://www.geocities.com/win32mutt/win32.html
> 
I meant that as a hint for _you_ to look. I don't have win32. It's open
source - take advantage of that.

Good luck,
Jurriaan
--

-- 
Join=20the=20campaign=20against=20excessive=20use=20of=20MIME=2e
Debian (Unstable) GNU/Linux 2.6.12-rc1-mm4 2x4734 bogomips load 0.02

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 2 comments |
headers
Alain Bench | 1 Apr 2005 23:51

Re: slrn observations with Giganews

Hello John,

 On Friday, March 25, 2005 at 7:10:39 PM -0500, John Gotts wrote:

> There doesn't seem to be a key to go to the first thread.

    "ESC <" by default, or <Home> key with this macro:

| define lln_article_bob () {
|   if (is_article_visible ())
|     call ("article_bob");
|   else
|     call ("header_bob");
| }
| definekey ("lln_article_bob","<Home>","article");

Bye!	Alain.
--

-- 
	The ad of the day will be about this:

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 0 comments |
headers
Lars Stokholm | 1 Apr 2005 22:24
Picon

Re: [Win32] Ctrl-G doesn't abort download of headers

Jurriaan wrote:

> I meant that as a hint for _you_ to look. I don't have win32. It's open
> source - take advantage of that.

I was afraid of that. I don't know where to start looking, and even if I found
something I'd have no idea what to do with it. I'm not lazy, just not capable.

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 1 comment |
headers
Troy Piggins | 3 Apr 2005 01:35

help with mimegpg macro

I am trying to write, or possibly hack an existing, macro that
detects a mime-gpg signed post and removes the lines that slrn
hasn't handled properly.  Unfortunately I have never written slang
before.

My question has a couple of parts - one to do with vim, but mostly
slang and slrn (versions in sig).

Background is from this post on the n.s.r group :
http://tinyurl.com/627bl

I have tried Tomasz Sienicki's macros with no success.  I thought I
would read his code, and try to use the parts of it that detect the
mime boundaries etc to serve my purposes.  When I started going
through the code, I noticed something odd with the brackets around
line 68 of his code from here:

http://cvs.pld-linux.org/cgi-bin/cvsweb/slrn-pl/macros/tsca-mymime.sl?rev=1.11

If I put the cursor on the first of the curly braces on line 68
which begins :
%{{{ multipart message

and in vim hit the '%' key, which should move the cursor to the
matching closing brace, it actually moves to a closing curly brace
on line 136.  Odd, because it isn't even a comment brace set.

On line 72 there appears to be an opening brace that is not closed,
and I thought this was the problem.  I inserted a closing curly
brace, and '%' then correctly matched the brace sets as expected.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Sven Guckes | 3 Apr 2005 03:33
Favicon

Re: help with mimegpg macro -> vim - 'matchpairs' only for pairs of single characters

* Troy Piggins <troy <at> piggo.com> [2005-04-03 03:24]:
> When I started going through the code, I noticed something
> odd with the brackets around line 68 of his code from here:
> http://cvs.pld-linux.org/cgi-bin/cvsweb/slrn-pl/macros/tsca-mymime.sl?rev=1.11
>
> If I put the cursor on the first of the curly braces on line 68
> which begins "%{{{ multipart message"
> and in vim hit the '%' key, which should move the cursor to the
> matching closing brace, it actually moves to a closing curly brace
> on line 136.  Odd, because it isn't even a comment brace set.

you expected to much, i'm afraid.  the '%' commands matches only pairs
of *single* characters - not strings like "%{{{" and "%}}}".  however,
matching of strings has been on the todo list for years now, though.

  :help todo
  7   Allow longer pairs in 'matchpairs'.  Use ~/vim/macros/matchit.vim as an
      example.

Sven

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 1 comment |
headers
Troy Piggins | 3 Apr 2005 03:58

Re: help with mimegpg macro -> vim - 'matchpairs' only for pairs of single characters

* Sven Guckes <maillist-slrn-user <at> guckes.net> :
> * Troy Piggins <troy <at> piggo.com> [2005-04-03 03:24]:
> > When I started going through the code, I noticed something
> > odd with the brackets around line 68 of his code from here:
> > http://cvs.pld-linux.org/cgi-bin/cvsweb/slrn-pl/macros/tsca-mymime.sl?rev=1.11
> >
> > If I put the cursor on the first of the curly braces on line 68
> > which begins "%{{{ multipart message"
> > and in vim hit the '%' key, which should move the cursor to the
> > matching closing brace, it actually moves to a closing curly brace
> > on line 136.  Odd, because it isn't even a comment brace set.
> 
> you expected to much, i'm afraid.  the '%' commands matches only pairs
> of *single* characters - not strings like "%{{{" and "%}}}".  however,
> matching of strings has been on the todo list for years now, though.
> 
>   :help todo
>   7   Allow longer pairs in 'matchpairs'.  Use ~/vim/macros/matchit.vim as an
>       example.

Ok, thanks Sven.  Looking at the code, though, it does appear there
is a brace missing, but as I mentioned I am a novice.  And the
matchpairs does seem to work on some of the other "%{{{" strings,
although maybe what you are saying is that those matches are a
fluke.

So that helps my vim part of the question.

--

-- 
T R O Y  P I G G I N S
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lars Stokholm | 13 Apr 2005 02:49
Picon

Problems compiling 0.9.8.1

I'm having trouble compiling 0.9.8.1 on one of my PCs. Same OS on both
of them (Ubuntu/Debian). It compiles fine on the other PC. I haven't
messes with the code.

art.c: In function `slrn_search_article':
art.c:759: error: storage size of `st' isn't known
art.c: In function `browse_url':
art.c:1157: error: `SLRL_DISPLAY_BUFFER_SIZE' undeclared (first use in
this func tion)
art.c:1157: error: (Each undeclared identifier is reported only once
art.c:1157: error: for each function it appears in.)
art.c: In function `article_search':
art.c:1198: error: `SLRL_DISPLAY_BUFFER_SIZE' undeclared (first use in
this func tion)
art.c:1198: error: storage size of `search_str' isn't known
art.c: In function `read_article':
art.c:2304: error: `SLang_Error' undeclared (first use in this function)
art.c: In function `check_for_current_article':
art.c:2742: error: `SLang_Error' undeclared (first use in this function)
art.c: In function `slrn_subject_strip_was':
art.c:2772: warning: assignment makes pointer from integer without a cast
art.c: In function `subject_skip_re':
art.c:2812: error: dereferencing pointer to incomplete type
art.c: In function `forward_article':
art.c:3006: error: `SLRL_DISPLAY_BUFFER_SIZE' undeclared (first use in
this func tion)
art.c: In function `next_header_same_subject':
art.c:3967: error: storage size of `st' isn't known
art.c:3969: error: `SLRL_DISPLAY_BUFFER_SIZE' undeclared (first use in
this func tion)
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jurriaan | 13 Apr 2005 07:11
Picon
Picon
Favicon

Re: Problems compiling 0.9.8.1

From: Lars Stokholm <lars.stokholm <at> gmail.com>
Date: Wed, Apr 13, 2005 at 02:49:45AM +0200
> I'm having trouble compiling 0.9.8.1 on one of my PCs. Same OS on both
> of them (Ubuntu/Debian). It compiles fine on the other PC. I haven't
> messes with the code.
> 
> art.c: In function `slrn_search_article':
> art.c:759: error: storage size of `st' isn't known
> art.c: In function `browse_url':
> art.c:1157: error: `SLRL_DISPLAY_BUFFER_SIZE' undeclared (first use in
> this func tion)

Could you get a fresh archive and double check that this shouldn't be
SLRN_DISPLAY_BUFFER_SIZE? If so, it reads like memory failure (bit
errors)....

Jurriaan
--

-- 
Fun will now commence.
	Seven of Nine
Debian (Unstable) GNU/Linux 2.6.12-rc2-mm2 2x4734 bogomips load 0.86

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Permalink | Reply | 3 comments |
headers
Lars Stokholm | 13 Apr 2005 13:50
Picon

Re: Problems compiling 0.9.8.1

Jurriaan wrote:
> Could you get a fresh archive and double check that this shouldn't be
> SLRN_DISPLAY_BUFFER_SIZE? If so, it reads like memory failure (bit
> errors)....

It says SLRL on both PCs and also in this archive:
ftp://ftp.fu-berlin.de/pub/unix/news/slrn/slrn-0.9.8.1.tar.bz2

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
Permalink | Reply | 2 comments |

Gmane