On 4/1/2024 5:16 PM, candycanearter07 wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>> dgold <d@gold.invalid> wrote:
>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>>> On 2024-03-28, candycanearter07
>>>> <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>>>>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>>>>> question. I haven't imagined it may be that difficult - seemingly
>>>>>> there are or were many flavors of readers but among them many
>>>>>> non-free or for windows or not supported anymore.
>>>>>>
>>>>>> But what about client?
>>>>>>
>>>>> I like slrn
>>>>
>>>> I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>>> That sold me.
>>>
>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>> always, uniformly, what comes to mind.
>>>
>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>> all possible.
>>
>> Same for tin. Just define your favourite editor - in my case (since
>> over four decades) vim - in your tinrc file. Forcing a user to use a
>> particular editor is rather silly.
>>
>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>
>> Nah, it's tin, The Ideal Newsreader! :-)
>
>
> Eh, tin is interesting but I prefer the visual thread display that slrn
> has.

maybe I finally should try out slrn

Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>>> dgold <d@gold.invalid> wrote:
>>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>> On 2024-03-28, candycanearter07
>>>>> <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>>> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>>>>>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>>>>>> question. I haven't imagined it may be that difficult - seemingly
>>>>>>> there are or were many flavors of readers but among them many
>>>>>>> non-free or for windows or not supported anymore.
>>>>>>>
>>>>>>> But what about client?
>>>>>>>
>>>>>> I like slrn
>>>>>
>>>>> I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>>>> That sold me.
>>>>
>>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>>> always, uniformly, what comes to mind.
>>>>
>>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>>> all possible.
>>>
>>> Same for tin. Just define your favourite editor - in my case (since
>>> over four decades) vim - in your tinrc file. Forcing a user to use a
>>> particular editor is rather silly.
>>>
>>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>>
>>> Nah, it's tin, The Ideal Newsreader! :-)
>>
>>
>> Eh, tin is interesting but I prefer the visual thread display that slrn
>> has.
>
> maybe I finally should try out slrn

It's pretty good.
--
user <candycane> is generated from /dev/urandom

candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>>> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>>>> dgold <d@gold.invalid> wrote:
>>>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>> On 2024-03-28, candycanearter07
>>>>>> <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>>>> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>>>>>>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>>>>>>> question. I haven't imagined it may be that difficult - seemingly
>>>>>>>> there are or were many flavors of readers but among them many
>>>>>>>> non-free or for windows or not supported anymore.
>>>>>>>>
>>>>>>>> But what about client?
>>>>>>>>
>>>>>>> I like slrn
>>>>>>
>>>>>> I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>>>>> That sold me.
>>>>>
>>>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>>>> always, uniformly, what comes to mind.
>>>>>
>>>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>>>> all possible.
>>>>
>>>> Same for tin. Just define your favourite editor - in my case (since
>>>> over four decades) vim - in your tinrc file. Forcing a user to use a
>>>> particular editor is rather silly.
>>>>
>>>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>>>
>>>> Nah, it's tin, The Ideal Newsreader! :-)
>>>
>>>
>>> Eh, tin is interesting but I prefer the visual thread display that slrn
>>> has.
>>
>> maybe I finally should try out slrn
>
>
> It's pretty good.

A agree with you, candy ;-)

LucLan <address@is.invalid> wrote at 15:56 this Wednesday (GMT):
> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>>> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>>>> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>>>>> dgold <d@gold.invalid> wrote:
>>>>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>>> On 2024-03-28, candycanearter07
>>>>>>> <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>>>>> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>>>>>>>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>>>>>>>> question. I haven't imagined it may be that difficult - seemingly
>>>>>>>>> there are or were many flavors of readers but among them many
>>>>>>>>> non-free or for windows or not supported anymore.
>>>>>>>>>
>>>>>>>>> But what about client?
>>>>>>>>>
>>>>>>>> I like slrn
>>>>>>>
>>>>>>> I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>>>>>> That sold me.
>>>>>>
>>>>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>>>>> always, uniformly, what comes to mind.
>>>>>>
>>>>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>>>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>>>>> all possible.
>>>>>
>>>>> Same for tin. Just define your favourite editor - in my case (since
>>>>> over four decades) vim - in your tinrc file. Forcing a user to use a
>>>>> particular editor is rather silly.
>>>>>
>>>>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>>>>
>>>>> Nah, it's tin, The Ideal Newsreader! :-)
>>>>
>>>>
>>>> Eh, tin is interesting but I prefer the visual thread display that slrn
>>>> has.
>>>
>>> maybe I finally should try out slrn
>>
>>
>> It's pretty good.
>
> A agree with you, candy ;-)

Thx
--
user <candycane> is generated from /dev/urandom

candycanearter07 wrote:

> LucLan <address@is.invalid> wrote at 15:56 this Wednesday (GMT):
>> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>>>> On 4/1/2024 5:16 PM, candycanearter07 wrote:

[...]

no sheriff here, but please, please, y'all kindly quote properly.

issdr <p_u_n_k_i_n_d@yahoo.it> wrote at 16:36 this Wednesday (GMT):
> candycanearter07 wrote:
>
>> LucLan <address@is.invalid> wrote at 15:56 this Wednesday (GMT):
>>> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>>>>> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>
> [...]
>
> no sheriff here, but please, please, y'all kindly quote properly.
>

What do you mean?
--
user <candycane> is generated from /dev/urandom

On 4/3/2024 7:00 PM, candycanearter07 wrote:
> issdr <p_u_n_k_i_n_d@yahoo.it> wrote at 16:36 this Wednesday (GMT):
>> candycanearter07 wrote:
>>
>>> LucLan <address@is.invalid> wrote at 15:56 this Wednesday (GMT):
>>>> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>>>>>> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>>
>> [...]
>>
>> no sheriff here, but please, please, y'all kindly quote properly.
>>
>
>
> What do you mean?

I think he implies he didn't shoot the deputy

On Wed, 3 Apr 2024 15:00:10 -0000 (UTC), candycanearter07
<candycanearter07@candycanearter07.nomail.afraid> wrote in
<uujqtq$469$1@dont-email.me>:

> Kyonshi <gmkeros@gmail.com> wrote at 13:55 this Wednesday (GMT):
>> On 4/1/2024 5:16 PM, candycanearter07 wrote:
>>> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>>>> dgold <d@gold.invalid> wrote:
>>>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>>>>> On 2024-03-28, candycanearter07
>>>>>> <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>>>>>> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>>>>>>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>>>>>>> question. I haven't imagined it may be that difficult - seemingly
>>>>>>>> there are or were many flavors of readers but among them many
>>>>>>>> non-free or for windows or not supported anymore.
>>>>>>>>
>>>>>>>> But what about client?
>>>>>>>>
>>>>>>> I like slrn
>>>>>>
>>>>>> I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>>>>> That sold me.
>>>>>
>>>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>>>> always, uniformly, what comes to mind.
>>>>>
>>>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>>>> all possible.
>>>>
>>>> Same for tin. Just define your favourite editor - in my case (since
>>>> over four decades) vim - in your tinrc file. Forcing a user to use a
>>>> particular editor is rather silly.
>>>>
>>>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>>>
>>>> Nah, it's tin, The Ideal Newsreader! :-)
>>>
>>>
>>> Eh, tin is interesting but I prefer the visual thread display that slrn
>>> has.
>>
>> maybe I finally should try out slrn
>
>
> It's pretty good.

Pan ain't bad either -- and it's in active development.

Another version bump just came down the pipe. They've been working
on generating the Makefiles with cmake (but Autoconf still works).

--
-v

vallor wrote:

[...]

,----[ https://www.lsu.edu/internet/usenet/usenet-etiquette.html ]
| Quote as little as possible from others' messages. This is the only
| major deviation between mail etiquette and news etiquette. Your news
| message may be sent to thousands of other sites. Most of these sites
| keep anywhere from several days to several weeks' worth of old news
| articles. This means that the article you are replying to is probably
| available, if someone needs to look at it. In particular, "me too"
| messages, where you quote several dozen lines from someone else's news
| article, and then add a one-line comment at the end are frowned
| upon. Make sure that all the quoted text is absolutely necessary.
`----

On Thu, 04 Apr 2024 10:06:37 +0200, issdr <p_u_n_k_i_n_d@yahoo.it> wrote
in <87il0xblgy.fsf@ID-313311.news.uni-berlin.de>:
> [...]

This doesn't apply to me, since I didn't "add a one-line comment".

Kindly redirect your net-nannying invective elsewhere.

--
-v

vallor wrote:

> On Thu, 04 Apr 2024 10:06:37 +0200, issdr <p_u_n_k_i_n_d@yahoo.it> wrote
> in <87il0xblgy.fsf@ID-313311.news.uni-berlin.de>:
>> [...]
>
> This doesn't apply to me, since I didn't "add a one-line comment".
>
> Kindly redirect your net-nannying invective elsewhere.

you got the point /s

alright, i give up

>On Wed, 03 Apr 2024 18:36:06 +0200, issdr <p_u_n_k_i_n_d@yahoo.it> wrote:

>no sheriff here, but please, please, y'all kindly quote properly.

In every group there's at least one self-appointed Park Ranger that
takes upon himself the duty of maintaining Good Order by making sure
everyone obeys the Rules and Regulations ordained by the Powers That
Be.

It all stems from them not getting that window monitor gig they wanted
so badly in the 6th grade.

They can't help it.

El Kabong wrote:

> In every group there's at least one self-appointed Park Ranger that
> takes upon himself the duty of maintaining Good Order by making sure
> everyone obeys the Rules and Regulations ordained by the Powers That
> Be.
>
> It all stems from them not getting that window monitor gig they wanted
> so badly in the 6th grade.
>
> They can't help it.

not my case, coherently with the premise i made. dude, look at the group you're
posting to tho, it's like shitting on surgeons' tables.

IAC enough for me, enjoy your eternal september.

>On Thu, 04 Apr 2024 14:05:00 +0200, issdr <p_u_n_k_i_n_d@yahoo.it> wrote:

>IAC enough for me, enjoy your eternal september.

Please don't go through with your threat to deprive us of your
expertise and guidance. Without your firm hand on the tiller directing
us, how would we know how to post? How would we know if we were
quoting incorrectly? We'd be lost! We'd decend into chaos! Saints
preserve us!

I think before anyone is allowed to post, it should be run by you so
you can check it for errors. Thank you for taking time out of your
busy day to go around pointing out others mistakes, no matter how
trivial. Everyone really appreciates it.

RodionGork <rodion_gork@mail.ru> wrote:
>
> But what about client?
>
> 1. I'm linux user so it should be available for linux
<snip>

As others have said: slrn. Pick whatever editor you like (vim
here). Been using this combination for decades.

For text-based, there's also tin, trn, etc. For those
recommending gnus, if you're already in the emacs universe, seems like
a natural choice.

The famous joke: Emacs is a great operating system. If only it
came with a good text editor too ;)

Phil
--
AH#61 Wolf#14 BS#89 bus#1 CCB#1 SENS KOTC#4
philb@philb.ca http://philb.ca

Phil Boutros <philb@philb.ca> writes:

> For text-based, there's also tin, trn, etc. For those
> recommending gnus, if you're already in the emacs universe, seems like
> a natural choice.

I'm cursing daily about Emacs' and GNUS' complexity, but I'm sure I'd
curse more without Emacs. E.g. Org-babel massively helps getting my
code centric notes done. That's like Jupyter Notebook on steroïds. And
that way I kind of already have caught my Emacs locked in syndrome, so
GNUS makes the most sense for me.

Th ROI only is significant when you use Emacs a lot, but then the
different "applications" in Emacs support each other and those effects
stack up like the modules involved, e.g. just "cd"-ing in Eshell to a
remote system as easy as changing a local dir. Or switching the mode of
the buffer to org while writing news and having the table commands or
code blocks at hand.

> The famous joke: Emacs is a great operating system. If only it
> came with a good text editor too ;)

See sig.

....aaaand another one:

| C-x C-c
| <...pause...>
| Ooops, wrong window!

--
I use BSDs, Linux, Haiku and other Emacs bootloaders.

On 2024-04-03, Kyonshi <gmkeros@gmail.com> wrote:

> maybe I finally should try out slrn

Better get in before Usenet slides downhill a little further :(

Andrew
--
You think that's air you're breathing now?

Phil Boutros <philb@philb.ca> wrote at 21:24 this Thursday (GMT):
[snip]
> The famous joke: Emacs is a great operating system. If only it
> came with a good text editor too ;)
>
>
> Phil

I can't wait for "emacs" to be released as its own distro.
--
user <candycane> is generated from /dev/urandom

candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
writes:

> I can't wait for "emacs" to be released as its own distro.

I already thought some Lisp cycles about using emacs' package manager
for own binaries too. "Own" as in "managing my $HOME", but I never
tried to implement it. It shouldn't have been too complicated as many
emacs "packages" already include C code that gets built at install time.

But on bad days I think GNU is all about EEE. Embrace, extend,
extinguish. Look at GCC: The GCCisms are so established now that even C
no longer is the universal portable assembler. Far too much stuff can
no longer be built using other compilers.

Writing my stuff in Org/Babel is not a locked in syndrome of the GCC
level. Org documents stay text and if all else fails, a human can read
and understand that.

I'm commuting between hating GNU and liking Org/Babel multipe times per
day.

--
I use BSDs, Linux, Haiku and other Emacs bootloaders.

yeti <yeti@tilde.institute> wrote at 19:55 this Friday (GMT):
> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
> writes:
>
>> I can't wait for "emacs" to be released as its own distro.
>
> I already thought some Lisp cycles about using emacs' package manager
> for own binaries too. "Own" as in "managing my $HOME", but I never
> tried to implement it. It shouldn't have been too complicated as many
> emacs "packages" already include C code that gets built at install time.
>
> But on bad days I think GNU is all about EEE. Embrace, extend,
> extinguish. Look at GCC: The GCCisms are so established now that even C
> no longer is the universal portable assembler. Far too much stuff can
> no longer be built using other compilers.
>
> Writing my stuff in Org/Babel is not a locked in syndrome of the GCC
> level. Org documents stay text and if all else fails, a human can read
> and understand that.
>
> I'm commuting between hating GNU and liking Org/Babel multipe times per
> day.

At least they don't seem as bad as Ubuntu?
--
user <candycane> is generated from /dev/urandom

On Sat, 6 Apr 2024 01:16:01 -0000 (UTC), candycanearter07 wrote:

> yeti <yeti@tilde.institute> wrote at 19:55 this Friday (GMT):
>> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
>> writes:
>>
>>> I can't wait for "emacs" to be released as its own distro.
>>
>> I already thought some Lisp cycles about using emacs' package manager
>> for own binaries too. "Own" as in "managing my $HOME", but I never
>> tried to implement it. It shouldn't have been too complicated as many
>> emacs "packages" already include C code that gets built at install
>> time.
>>
>> But on bad days I think GNU is all about EEE. Embrace, extend,
>> extinguish. Look at GCC: The GCCisms are so established now that even
>> C no longer is the universal portable assembler. Far too much stuff
>> can no longer be built using other compilers.
>>
>> Writing my stuff in Org/Babel is not a locked in syndrome of the GCC
>> level. Org documents stay text and if all else fails, a human can read
>> and understand that.
>>
>> I'm commuting between hating GNU and liking Org/Babel multipe times per
>> day.
>
>
> At least they don't seem as bad as Ubuntu?

Ubuntu what is? Debian simply it is, isn't it?

--
De Kerk van Roodkapje (KvR) belijdt de enige ware religie! De
Rode Macht van Roodkapje is wetenschappelijk onderzocht en
bevestigd [1][2][3].

[1] https://nl.wikipedia.org/wiki/Roodverschuiving
[2] https://logos.nl/roodverschuiving-van-sterrenlicht/
[3] https://nl.wikipedia.org/wiki/Wet_van_Hubble-Lema%C3%AEtre

On 2024-03-28, RodionGork <rodion_gork@mail.ru> wrote:
> But what about client? 1. I'm linux user so it should be available
> for linux 3. It would be good if it is lightweight enough (Thunderbird
> seems a bit too fat already but not too much if you say it is
> definitely the best choice). 4. It would be all right if it is works
> in text-mode lacking fancy features for handling images and videos
> etc.

slrn

You don't mention what Linux distro you use but I'd guess slrn is
packaged for the most popular ones.

--
Antti Talsta

RonB <ronb02NOSPAM@gmail.com> writes:

> On 2024-03-29, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>> Bud Frede <frede@mouse-potato.com> wrote at 19:09 this Friday (GMT):
>>> Marco Moock <mm+usenet-es@dorfdsl.de> writes:
>>>
>>>> On 28.03.2024 um 06:33 Uhr RodionGork wrote:
>>>>
>>>>
>>>>> 4. It would be all right if it is works in text-mode
>>>>> lacking fancy features for handling images and videos etc.
>>>>
>>>> tin, slrn, trn exist.
>>>
>>> I've used all 3, and actually used slrn for a number of years. I finally
>>> decided to jump into gnus though, and once I did I wish I had done it
>>> years earlier.
>>>
>>> I had found that things like tin, trn, and slrn each had limitations for
>>> me. Sometimes there were workarounds and sometimes not. With gnus, every
>>> time I wondered about a feature, I found it was already there or there
>>> was an easy way of making gnus do that.
>>>
>>> I feel that gnus is the most capable and flexible newsreader, and I'd
>>> find it hard to go back to anything else.
>>
>>
>> GNUs certainly seems interesting, but I also don't want to go down the
>> emacs route.
>
> I'm too old to (want to) learn another one and I like using slrn with Jstar.

I didn't have to learn that much emacs to be able to use gnus. In fact,
I already knew some emacs because of the defaults for readline on most
distros.

In addition, if you really want to use a different editor with gnus, you
can. I used to know a guy who used gnus with vim.

I typically use vim (neovim) for most editing. I only really use emacs
for gnus at this point. I've thought about using emacs more, but I'm ok
with the way things are currently.

candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
writes:

> Frank Slootweg <this@ddress.is.invalid> wrote at 13:45 this Sunday (GMT):
>> dgold <d@gold.invalid> wrote:
>>> On 2024-03-28, RonB <ronb02NOSPAM@gmail.com> wrote:
>>> > On 2024-03-28, candycanearter07
>>> > <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>> >> RodionGork <rodion_gork@mail.ru> wrote at 06:33 this Thursday (GMT):
>>> >>> Hi Friends and sorry for such a trivial and perhaps frequently-asked
>>> >>> question. I haven't imagined it may be that difficult - seemingly
>>> >>> there are or were many flavors of readers but among them many
>>> >>> non-free or for windows or not supported anymore.
>>> >>>
>>> >>> But what about client?
>>> >>>
>>> >> I like slrn
>>> >
>>> > I do too. I can pick Jstar (WordStar variant of JOE) as my editor.
>>> > That sold me.
>>>
>>> It's so strange to me -- anytime anyone asks what Usenet is, slrn is
>>> always, uniformly, what comes to mind.
>>>
>>> I'm editing this in Vim; Ron edited his answer in Jstar; CC07 could have
>>> used nano or emacs or whatever -- the point remains: slrn just makes it
>>> all possible.
>>
>> Same for tin. Just define your favourite editor - in my case (since
>> over four decades) vim - in your tinrc file. Forcing a user to use a
>> particular editor is rather silly.
>>
>>> Slrn, always, forever. It is usenet. Hasta la slrn siempre.
>>
>> Nah, it's tin, The Ideal Newsreader! :-)
>
>
> Eh, tin is interesting but I prefer the visual thread display that slrn
> has.

trn anyone? :-)

I started reading news with rn and then nn. Then I did SOUP packets via
uqwk and yarn/2 as my newsreader.

I did use slrn for a number of years, but as I said, I found it limiting
in some ways and switched to gnus instead. There was a learning curve,
but there was when I first started using slrn too.

I've revisited slrn a couple of times, but I no longer found it to be a
familiar and comfortable place. I didn't stay long and went back to
gnus.

El Kabong <Quickdraw@HannaBarbera.com> writes:

>>On Thu, 28 Mar 2024 15:40:09 -0000 (UTC), candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>
>>I like slrn
>
> I used slrn when I was using Linux, BSD, OS/2, and Windows at the same
> time. It worked the same everywhere.
>
> I went back to Agent because, for me, Forte Agent=Usenet.
> I'm an old warez hound and have been pulling headers in Agent almost
> every day since 1995.

I used Agent at one time, and I was on their beta team for a number of
years. I used to test it with wine just for kicks although I had stopped
using it for actual newsreading long before.

It was pretty old and crusty even 20 years ago, and the changes they
made to it never really helped. It was designed in Win 3.x days and
it showed.

It was also broken in some ways from the very beginning, and they never
fixed it. (It never handled cross-posted articles properly, for
example.) I don't think they could have really fixed it without starting
from scratch, and they weren't willing to do that.