slrn-user — Public discussion of the slrn newsreader

patch to use tcp keepalive

[Tilmann H. <0x...@di...>]

------- =_NTBCN0IzNkQ2NkQwN0FFRkYwRUJGM0U5NzQ4MUM1QkM=
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
              charset="UTF-8"
Content-Transfer-Encoding: 8bit

Patch to use tcp keepalive, so the server does not hang up the connection
when being idle. Perhaps it is useful to somebody else.

diff --git a/src/sltcp.c b/src/sltcp.c
index 40ada13..937b441 100644
--- a/src/sltcp.c
+++ b/src/sltcp.c
@@ -78,6 +78,8 @@
 # include <arpa/inet.h>
 #endif
 
+#include <netinet/tcp.h>
+
 #if !defined(h_errno) && !defined(__CYGWIN__)
 extern int h_errno;
 #endif
@@ -201,6 +203,10 @@ static int sys_call_interrupted_hook (void) /*{{{*/
  */
 static int get_tcp_socket_1 (char *host, int port) /*{{{*/
 {
+   int keepalive = 1;
+   int keepidle = 60;
+   int keepcnt = 5;
+   int keepintvl = 5;
 #ifdef HAVE_GETADDRINFO
    /* Be AF-independent, so IPv6 works as well */
    int fd;
@@ -279,6 +285,14 @@ static int get_tcp_socket_1 (char *host, int port) /*{{{*/
 	    print_error ("Error creating socket: %s\n", strerror(errno));
 	 }
       } else {
+	    if (setsockopt(fd, SOL_SOCKET, SO_KEEPALIVE, &keepalive, sizeof(keepalive))
+	    || setsockopt(fd, SOL_TCP, TCP_KEEPIDLE, &keepidle, sizeof(keepidle))
+	    || setsockopt(fd, SOL_TCP, TCP_KEEPCNT, &keepcnt, sizeof(keepcnt))
+	    || setsockopt(fd, SOL_TCP, TCP_KEEPINTVL, &keepintvl, sizeof(keepintvl))) {
+           if (TCP_Verbose_Reporting) {
+              print_error ("Error setting socket option: %s\n", strerror(errno));
+           }
+        }
 	 if (TCP_Verbose_Reporting) {
 	    print_error ("Created socket; descriptor is = %i\n", fd);
 	 }
@@ -368,6 +382,10 @@ static int get_tcp_socket_1 (char *host, int port) /*{{{*/
 	perror("socket");
 	return -1;
      }
+   setsockopt(fd, SOL_SOCKET, SO_KEEPALIVE, &keepalive, sizeof(keepalive));
+   setsockopt(fd, SOL_TCP, TCP_KEEPIDLE, &keepidle, sizeof(keepidle));
+   setsockopt(fd, SOL_TCP, TCP_KEEPCNT, &keepcnt, sizeof(keepcnt));
+   setsockopt(fd, SOL_TCP, TCP_KEEPINTVL, &keepintvl, sizeof(keepintvl)));
 
    not_connected = -1;
 

------- =_NTBCN0IzNkQ2NkQwN0FFRkYwRUJGM0U5NzQ4MUM1QkM=
MIME-Version: 1.0
Content-Disposition: attachment
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iIsEABYKADMWIQR8dCBKfJM4KiPu/Jxq+QIoQiEKkwUCaY9RURUcMHhjYWZlQGRp
cmVjdGJveC5jb20ACgkQavkCKEIhCpMU4AEAjBdsWL/onPtb1FU7z2rwi+YjZ1N1
+V9+WJ4rursvozoBAKgIY2EnJ9O7l83GGRMq4/Ytb9KbTjOKCGJfavlQg2AG
=TRpl
-----END PGP SIGNATURE-----

------- =_NTBCN0IzNkQ2NkQwN0FFRkYwRUJGM0U5NzQ4MUM1QkM=--

patch to compile slrn pre1.0.4-6 from git origin/master

[Tilmann H. <0x...@di...>]

------- =_MEVFRTZBREEwMTQ1MDVCNTY1MDZCODYyRDlBRURDNTM=
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
              charset="UTF-8"
Content-Transfer-Encoding: 8bit

diff --git a/src/misc.c b/src/misc.c
index d6b1886..7319cec 100644
--- a/src/misc.c
+++ b/src/misc.c
@@ -373,7 +373,7 @@ void slrn_verror (char *fmt, va_list ap)
 {
    va_list ap1;
 
-   VA_COPY(ap1, ap);
+   va_copy(ap1, ap);
 
    if ((Slrn_TT_Initialized & SLRN_SMG_INIT) == 0)
      {

------- =_MEVFRTZBREEwMTQ1MDVCNTY1MDZCODYyRDlBRURDNTM=
MIME-Version: 1.0
Content-Disposition: attachment
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iIsEABYKADMWIQR8dCBKfJM4KiPu/Jxq+QIoQiEKkwUCaY9QiBUcMHhjYWZlQGRp
cmVjdGJveC5jb20ACgkQavkCKEIhCpNZGgEA5PaMCkZ0CTanMkJ7uu3Mh77c2ebL
637S2d6GKfsvNAABANOBGISAVYONCyPQkx55ah3JuskvZ9YtsqdK7opRPYwI
=TQwQ
-----END PGP SIGNATURE-----

------- =_MEVFRTZBREEwMTQ1MDVCNTY1MDZCODYyRDlBRURDNTM=--

Re: basic configuration.

[Martin T. <tr...@gm...>]

On 19.12.25 18:12, Anthony Azzopardi wrote:
> Thank you for your response, but sorry to say I did not connect. I > got this error: > > └─$ slrn slrn 1.0.3 > > Loading
/usr/share/slrn/slang/slrn.sl <http://slrn.sl> Reading > startup file
/etc/news/slrn.rc.slrn fatal error: Unable to find a > valid hostname
for constructing your e-mail address. You probably > want to specify a
hostname in your .slrnrc file. Please see the > "slrn reference manual"
for full details.
As it says, you have to finish the hostname

> There are some more values which you might to define in > your .slrnrc, such as > > set hostname > set username mine are

set hostname    "gmx.net"
set username    "t-usenet"

However, hostname also may refer to your newsserver setup for
nnrpaccess  news.eternal-september.org  YOURID YOURPASSWORD

Re: basic configuration.

[Anthony A. <twa...@gm...>]

Thank you for your response, but sorry to say I did not connect. I got this
error:

└─$ slrn
slrn 1.0.3

Loading /usr/share/slrn/slang/slrn.sl
Reading startup file /etc/news/slrn.rc.slrn fatal error:
Unable to find a valid hostname for constructing your e-mail address.
You probably want to specify a hostname in your .slrnrc file.
Please see the "slrn reference manual" for full details.




On Fri, Dec 19, 2025 at 5:00 PM Martin Trautmann via Slrn-user <
slr...@li...> wrote:

> On 19.12.25 16:51, Martin Trautmann wrote:
> > On 19.12.25 16:46, Anthony Azzopardi wrote: >> Hi list, >> >> Is there a
> very basic configuration slrn.rc to use news.eternal- >> september.org
> <http://news.eternal-september.org> <http://news.eternal-september.org>,
> and read >> comp.lang.c? > > yes
> but since I guess you want more details, get any sample .slrnrc file.
>
> Add
> server  "news.eternal-september.org"    ".jnewsrc.es"
> nnrpaccess  news.eternal-september.org  YOURID YOURPASSWORD
>
> And create a file .jnewsrc.es which includes
>
> comp.lang.c: 1-72026
> comp.lang.c++: 1-44744,155145
> comp.lang.c++.misc: 1-2
> comp.lang.c++.moderated: 1-12744
> comp.lang.c.moderated: 1-1971
>
> (although this file will be auto edited, once you download a list of all
> newsgroups, subscribe to some and set some as read)
>
> I use .jnewsrc plus two letters in order to access different news servers
>
> There are some more values which you might to define in your .slrnrc, such
> as
>
> set hostname
> set username
> set replyto
> set realname    "Martin Τrautmann"
> set generate_message_id         1
> set generate_date_header 1
>
>

Re: basic configuration.

[Martin T. <tr...@gm...>]

On 19.12.25 16:51, Martin Trautmann wrote:
> On 19.12.25 16:46, Anthony Azzopardi wrote: >> Hi list, >> >> Is there a very basic configuration slrn.rc to use
news.eternal- >> september.org <http://news.eternal-september.org>, and
read >> comp.lang.c? > > yes
but since I guess you want more details, get any sample .slrnrc file.

Add 
server  "news.eternal-september.org"    ".jnewsrc.es"
nnrpaccess  news.eternal-september.org  YOURID YOURPASSWORD

And create a file .jnewsrc.es which includes

comp.lang.c: 1-72026
comp.lang.c++: 1-44744,155145
comp.lang.c++.misc: 1-2
comp.lang.c++.moderated: 1-12744
comp.lang.c.moderated: 1-1971

(although this file will be auto edited, once you download a list of all
newsgroups, subscribe to some and set some as read)

I use .jnewsrc plus two letters in order to access different news servers

There are some more values which you might to define in your .slrnrc,
such as

set hostname    
set username    
set replyto     
set realname    "Martin Τrautmann"
set generate_message_id         1
set generate_date_header 1

Re: basic configuration.

[Martin T. <tr...@gm...>]

On 19.12.25 16:46, Anthony Azzopardi wrote:
> Hi list, > > Is there a very basic configuration slrn.rc to use news.eternal- >
september.org <http://news.eternal-september.org>, and read >
comp.lang.c? yes

basic configuration.

[Anthony A. <twa...@gm...>]

Hi list,

Is there a very basic configuration slrn.rc to use
news.eternal-september.org, and read comp.lang.c?

Thank you,
Anthony.

Re: which shortcut to unsubscribe from all groups

[Martin T. <tr...@gm...>]

On 11.02.25 13:48, hymie! via Slrn-user wrote:
> > which keyboard shortcut is it that does unsubscribe you from all
> > subscribed groups - and how do I disable that one?
>
> I don't see that option in the help menus, but I do see...
>
>   u                       Unsubscribe from the current newsgroup.
>       ESC 1 u             Unsubscribe from groups matching a pattern.
>   l                       Toggle display of groups without unread articles.
>   L                       Toggle listing of unsubscribed groups.
>       ESC 1 L             Hide unsubscribed groups.
>       ESC 2 L             Show unsubscribed groups.
>
> My best guess is that you hit esc-1-u and gave a blank pattern ?

Maybe - I sometimes use esc-1-p. Esc-1 could also be where  my hand
might rest, then a blank. But I tried esc-1-blank and nothing happened.
> Anyway, the "Show unsubscribed groups" might help you rebuild your
> .jnewsrc after a mistake.

I'll have to understand esc-2-L first. It just shows all unsubscribed
groups, but not just those I had subscribed to before.:

Re: which shortcut to unsubscribe from all groups

[hymie! <hy...@na...>]

> which keyboard shortcut is it that does unsubscribe you from all
> subscribed groups - and how do I disable that one?

I don't see that option in the help menus, but I do see...

  u                       Unsubscribe from the current newsgroup.
      ESC 1 u             Unsubscribe from groups matching a pattern.
  l                       Toggle display of groups without unread articles.
  L                       Toggle listing of unsubscribed groups.
      ESC 1 L             Hide unsubscribed groups.
      ESC 2 L             Show unsubscribed groups.

My best guess is that you hit esc-1-u and gave a blank pattern ?

Anyway, the "Show unsubscribed groups" might help you rebuild your
.jnewsrc after a mistake.

--hymie!

which shortcut to unsubscribe from all groups

[Martin T. <tr...@gm...>]

Hi,

which keyboard shortcut is it that does unsubscribe you from all
subscribed groups - and how do I disable that one?

It now happened for the second time to me that I ended up with a
completely empty newsreader within a few weeks - and I don't know how
that happened.

I could rebuild my .jnewsrc file more or less from former .jnewsrc files
from other news servers. But I don't want to do that regularly.

I can't remember that this ever happened with former versions of slrn.
So I guess it's a newer functionality that had been added to recent
releases.

Thanks,
Martin

Re: bug report: http://slrn.sourceforge.net/data/ and slrnrc-conv

[<hy...@na...>]

I found a copy that hopefully will help you.

--hymie!

Martin Trautmann via Slrn-user writes:
>Hi all,
>
>I just had to re-install slrn. I now get the report
>
>! Your configuration file contains obsolete commands or function names that
>! will not be supported by future versions of this program.
>! If you have Perl installed, you can use the script slrnrc-conv to change
>! your configuration accordingly.=C2=A0 It can be found in the source distribution
>! or retrieved from <URL:http://slrn.sourceforge.net/data/>.
>

Re: bug report: http://slrn.sourceforge.net/data/ and slrnrc-conv

[Martin T. <tr...@gm...>]

On 22.01.25 18:04, hy...@na... wrote:
> I found a copy that hopefully will help you.

thanks, done!

bug report: http://slrn.sourceforge.net/data/ and slrnrc-conv

[Martin T. <tr...@gm...>]

Hi all,

I just had to re-install slrn. I now get the report

! Your configuration file contains obsolete commands or function names that
! will not be supported by future versions of this program.
! If you have Perl installed, you can use the script slrnrc-conv to change
! your configuration accordingly.  It can be found in the source
distribution
! or retrieved from <URL:http://slrn.sourceforge.net/data/>.


This link to http://slrn.sourceforge.net/data/> does no longer work

Maybe this should be fixed sometime.

Is the perl script still available anywhere?

slrn 1.0.3
S-Lang Library Version: 2.3.3
Operating System: Darwin


Schönen Gruß
Martin

Greetings from Italy and lost messages

[Gianfranco B. <gbe...@gm...>]

Hallo,

   and excuse for my poor english.

   Now it's one or two years that I noticed that my slrn+slrnpull doesn't
download all the messages. It seems in a random way, no regularity, so
some messages in different threads are present and some (also mine) are
not.

   I tried sylpheed with the same configuration (aioe for now, but it
happens also with others) and it works, I can see more messages than in
slrn.

   Someone has the same problem? Have you suggestion about it? I'd like
to continue to use slrn, if it's possible.

   Thank you. :-)


-- 
Gianfranco Bertozzi

Slrn posting are blank

[Duke N. <duk...@gm...>]

I'm having trouble posting anything from slrn.
Doesn't matter if I use Jed/emacs/nano/whatever my posts DO get
sent, but they are all blank. Nothing that I wrote gets sent. As if
the text never leaves the editor.

Clues please.
--
Duke
** Text only please. Bottom post is best for me **

Re: Can't compile the latest version of slrn on raspbian

[Adam F. <a2...@du...>]

On 2021-12-23, hy...@na... wrote:

> Adam Funk writes:
>>Currently using:
>>
>>$ /usr/local/bin/slrn --version
>>slrn pre1.0.4-2
>>        * Note: This version is a developer preview.
>>S-Lang Library Version: 2.3.2
>>        * Note: This program was compiled against version 2.3.0.
>>Operating System: Linux
>>
>>/usr/bin/ld: server.o: in function `alloc_ssl':
>>/home/adam/software/slrn/src/sltcp.c:566: undefined reference to `SSL_library_
>>init'
>>/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:567: undefined reference to 
>>`SSLv23_client_method'
>>/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:569: undefined reference to 
>>`SSL_load_error_strings'
>
>>ii  openssl                              1.1.1k-1+deb11u1 armhf        Secure 
>>Sockets Layer toolkit - cryptographic utility
>
> I don't want to say this authoritatively, but I understand that openssl
> versions 1.1 are not fully backward-compatible with versions 1.0 .
> I would not be surprised to learn that slrn is too old for the changes
> in openssl 1.1 .
>
> You might either need to find an older version, or (as i did) leave out
> --with-ssl

You're right:

$ ./configure --with-canlock --enable-spool --with-uu
$ make
$ sudo make install
$ slrn --version
slrn pre1.0.4-6
        * Note: This version is a developer preview.
S-Lang Library Version: 2.3.2
Operating System: Linux

COMPILE TIME OPTIONS:
 Backends: +nntp -slrnpull +spool
 External programs / libs: +canlock -inews -ssl -uudeview +iconv
 Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
    -grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
 Using 64 bit integers for article numbers.

DEFAULTS:
 Default server object:     nntp
 Default posting mechanism: nntp

I'd forgotten about SSL libraries being in knots --- thanks!

Re: Can't compile the latest version of slrn on raspbian

[<hy...@na...>]

Adam Funk writes:
>Currently using:
>
>$ /usr/local/bin/slrn --version
>slrn pre1.0.4-2
>        * Note: This version is a developer preview.
>S-Lang Library Version: 2.3.2
>        * Note: This program was compiled against version 2.3.0.
>Operating System: Linux
>
>/usr/bin/ld: server.o: in function `alloc_ssl':
>/home/adam/software/slrn/src/sltcp.c:566: undefined reference to `SSL_library_
>init'
>/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:567: undefined reference to 
>`SSLv23_client_method'
>/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:569: undefined reference to 
>`SSL_load_error_strings'

>ii  openssl                              1.1.1k-1+deb11u1 armhf        Secure 
>Sockets Layer toolkit - cryptographic utility

I don't want to say this authoritatively, but I understand that openssl
versions 1.1 are not fully backward-compatible with versions 1.0 .
I would not be surprised to learn that slrn is too old for the changes
in openssl 1.1 .

You might either need to find an older version, or (as i did) leave out
--with-ssl

--hymie!

Can't compile the latest version of slrn on raspbian

[Adam F. <a2...@du...>]

Currently using:

$ /usr/local/bin/slrn --version
slrn pre1.0.4-2
        * Note: This version is a developer preview.
S-Lang Library Version: 2.3.2
        * Note: This program was compiled against version 2.3.0.
Operating System: Linux

COMPILE TIME OPTIONS:
 Backends: +nntp -slrnpull -spool
 External programs / libs: +canlock -inews +ssl -uudeview +iconv
 Features: +decoding +emphasized_text +end_of_thread +fake_refs +gen_msgid
    -grouplens -msgid_cache +piping +rnlock +spoilers -strict_from
 Using 64 bit integers for article numbers.

DEFAULTS:
 Default server object:     nntp
 Default posting mechanism: nntp

Trying to compile the latest version:

$ git remote -vv
origin  git://git.jedsoft.org/git/slrn.git (fetch)
origin  git://git.jedsoft.org/git/slrn.git (push)

$ git pull
Already up to date.

$ ./configure --with-canlock --with-ssl --enable-spool --with-uu
# config options that worked last time
# no errors

$ make
# ...
/usr/bin/ld: server.o: in function `alloc_ssl':
/home/adam/software/slrn/src/sltcp.c:566: undefined reference to `SSL_library_init'
/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:567: undefined reference to `SSLv23_client_method'
/usr/bin/ld: /home/adam/software/slrn/src/sltcp.c:569: undefined reference to `SSL_load_error_strings'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:120: /home/adam/software/slrn/src/objs/slrn] Error 1
make[1]: Leaving directory '/home/adam/software/slrn/src'
make: *** [Makefile:8: all] Error 2

I have the following ssl-related packages installed:

$ dpkg -l '*ssl*' |grep ^i
ii  libio-socket-ssl-perl                2.069-1          all          Perl module implementing object oriented interface to SSL sockets
ii  libnet-smtp-ssl-perl                 1.04-1           all          Perl module providing SSL support to Net::SMTP
ii  libnet-ssleay-perl                   1.88-3+b1        armhf        Perl module for Secure Sockets Layer (SSL)
ii  libssl-dev:armhf                     1.1.1k-1+deb11u1 armhf        Secure Sockets Layer toolkit - development files
ii  libssl1.0.0:armhf                    1.0.1t-1+deb8u7  armhf        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:armhf                      1.1.1k-1+deb11u1 armhf        Secure Sockets Layer toolkit - shared libraries
ii  openssl                              1.1.1k-1+deb11u1 armhf        Secure Sockets Layer toolkit - cryptographic utility
ii  perl-openssl-defaults:armhf          5                armhf        version compatibility baseline for Perl OpenSSL packages
ii  ssl-cert                             1.1.0+nmu1       all          simple debconf wrapper for OpenSSL

Could someone please tell me how to fix this?

Thanks,
Adam

Re: ./configure bugs on OS X

[Christian E. <bc...@ph...>]

* Daniel Macks on Thursday, June 10, 2021 at 07:05:24 -0400:
> Building slrn-1.0.3a fails on recent OS X because the compiler treats implicit function declarations as errors, which causes some ./configure tests to fail to detect features that actually exist on this platform:
> 
> : checking for an implementation of va_copy()... no
> : checking for an implementation of __va_copy()... no
> : checking whether va_lists can be copied by value... no
> 
> Those first two should be "yes". According to config.log, the problems look like:
> 
> : conftest.c:93:4: error: implicitly declaring library function 'exit' with type 'void (int) __attribute__((noreturn))'
> :           exit (1);
> :           ^
> : conftest.c:93:4: note: include the header <stdlib.h> or explicitly provide a declaration for 'exit'
> 
> Putting '#include <stdlib.h>' (not just stdarg.h) in the AC_ VA_COPY function fixes it.

I can confirm that this fixes the problem.

-- 
https://instagram.com/christianebertphotos

Re: Refreshing Message headers

[Christian E. <bc...@ph...>]

* Duke Normandin on Monday, November 22, 2021 at 20:11:17 -0700:
> slrn fatal error:
> /home/dnormandin/.slrnrc: Error encountered processing line 3
> interpret "refresh-in-article-mode.sl"
> 
> The top of my .slrnrc has:
> 
> % -*- slang -*-
> set macro_directory "${HOME}/News/macros"

As Tavis said: just use News/macros

man slrn says:

SLRNHOME
       When  interpreting  filenames  as  relative to your home directory, slrn
       uses this variable to find out what your home directory is.  If $SLRNHOME
       is unset, $HOME is used instead.

In Message-Id: <202...@gm...> 
you wrote:

| Loading /usr/share/slrn/slang/refresh-in-article-mode.sl

I actually tried to 'misplace' my script to reproduce, but got a 
slightly different error.

You can check your config with:

slrn --show-config | grep -F macro_directory

> interpret "refresh-in-article-mode.sl"
> 
> Is there something wrong with these three lines?

See above.

-- 
LAST SHIP HOME                      --->> https://lastshiphome.de
Official Selection                          DOK.fest München 2018
German Ocean Film Award                        CineMare Kiel 2019
Best Documentary Feature   Wales International Film Festival 2020

Re: Refreshing Message headers

[Tavis O. <ta...@gm...>]

On 2021-11-23, Duke Normandin wrote:
> On Tue, 23 Nov 2021 01:29:04 +0100
> Christian Ebert <bc...@ph...> wrote:
>
> Nope! No Joy! Not a permissions issue. The file _is_ being read!
>
> The error msg is:
> slrn fatal error:
> /home/dnormandin/.slrnrc: Error encountered processing line 3
> interpret "refresh-in-article-mode.sl"
>
> The top of my .slrnrc has:
>
> % -*- slang -*-
> set macro_directory "${HOME}/News/macros"
> interpret "refresh-in-article-mode.sl"
>
> Is there something wrong with these three lines?

I don't think slrn understands environment variables in paths like that,
I think you can just remove it, i.e. set macro_directory "News/macros"

What is the message before the "slrn fatal error"?

Tavis.

-- 
 _o)            $ lynx lock.cmpxchg8b.com
 /\\  _o)  _o)  $ finger ta...@sd...
_\_V _( ) _( )  @taviso

Re: Refreshing Message headers

[Duke N. <duk...@gm...>]

On Tue, 23 Nov 2021 01:29:04 +0100
Christian Ebert <bc...@ph...> wrote:

> * Duke Normandin on Monday, November 22, 2021 at 10:09:38 -0700:
> >> Which S-Lang version do you have?
> >
> > ─› slsh --version
> > slsh version 0.9.4-0; S-Lang version: 2.3.2
> >
> >> Older, or rather: ancient, versions did not have the ||
> >> operator, you'd have to replace it with orelse in the script.
> >
> > I believe that I have a fairly recent version?
>
> Sure. Was just a shot in the dark.
>
> For testing did you try to load another (shipped) script you have
> in /usr/share/slang/slrn/slang/ ?
>
> Permissions of the header refresh script might also be worth
> checking.
>
> I'm also attaching the script I am using, just to make sure that
> there are no copy & paste glitches.

Nope! No Joy! Not a permissions issue. The file _is_ being read!

The error msg is:
slrn fatal error:
/home/dnormandin/.slrnrc: Error encountered processing line 3
interpret "refresh-in-article-mode.sl"

The top of my .slrnrc has:

% -*- slang -*-
set macro_directory "${HOME}/News/macros"
interpret "refresh-in-article-mode.sl"

Is there something wrong with these three lines?
--
Duke

Re: Refreshing Message headers

[Duke N. <duk...@gm...>]

On Tue, 23 Nov 2021 01:29:04 +0100
Christian Ebert <bc...@ph...> wrote:

> * Duke Normandin on Monday, November 22, 2021 at 10:09:38 -0700:
> >> Which S-Lang version do you have?
> >
> > ─› slsh --version
> > slsh version 0.9.4-0; S-Lang version: 2.3.2
> >
> >> Older, or rather: ancient, versions did not have the ||
> >> operator, you'd have to replace it with orelse in the script.
> >
> > I believe that I have a fairly recent version?
>
> Sure. Was just a shot in the dark.
>
> For testing did you try to load another (shipped) script you have
> in /usr/share/slang/slrn/slang/ ?
>
> Permissions of the header refresh script might also be worth
> checking.
>
> I'm also attaching the script I am using, just to make sure that
> there are no copy & paste glitches.

Thanks a bunch for all your trouble! BTW, how do you like
programming using S-LANG? Just curious. Not much traffic or
opinions on the slang-users ML
--
Duke

Re: Refreshing Message headers

[Christian E. <bc...@ph...>]

* Duke Normandin on Monday, November 22, 2021 at 10:09:38 -0700:
>> Which S-Lang version do you have?
>
> ─› slsh --version
> slsh version 0.9.4-0; S-Lang version: 2.3.2
>
>> Older, or rather: ancient, versions did not have the || operator,
>> you'd have to replace it with orelse in the script.
>
> I believe that I have a fairly recent version?

Sure. Was just a shot in the dark.

For testing did you try to load another (shipped) script you have 
in /usr/share/slang/slrn/slang/ ?

Permissions of the header refresh script might also be worth 
checking.

I'm also attaching the script I am using, just to make sure that 
there are no copy & paste glitches.

Gook luck!

-- 
LAST SHIP HOME
Winner of the German Ocean Film Award 2019
--->> https://lastshiphome.de/en

Re: Refreshing Message headers

[Duke N. <duk...@gm...>]

On Mon, 22 Nov 2021 16:51:50 +0100
Christian Ebert <bc...@ph...> wrote:

> * Duke Normandin on Friday, November 19, 2021 at 11:19:09 -0700:
> > On Tue, 2 Nov 2021 07:47:08 +0000
> > Christian Ebert <bc...@ph...> wrote:
> >
> > [snip]

> No idea what's going wrong there. Definitely works for me™.
>
> Which S-Lang version do you have?

─› slsh --version
slsh version 0.9.4-0; S-Lang version: 2.3.2

> Older, or rather: ancient, versions did not have the || operator,
> you'd have to replace it with orelse in the script.

I believe that I have a fairly recent version?

Thx for your reply!
--
Duke