• newsreader for M1

    From Gavin G@ggrandish@gmail.com to comp.sys.mac.system on Friday, January 01, 2021 18:04:48
    From Newsgroup: comp.sys.mac.system

    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.
    Thanks.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Savageduck@savageduck1@removespam.me.com to comp.sys.mac.system on Friday, January 01, 2021 20:18:59
    From Newsgroup: comp.sys.mac.system

    On Jan 1, 2021 at 6:04:48 PM PST, "Gavin G" <ggrandish@gmail.com> wrote:

    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.
    Thanks.

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>
    --
    Regards,
    Savageduck


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From =?UTF-8?B?S2lyw6FseQ==?=@kiraly@spamsucks.ca to comp.sys.mac.system on Saturday, January 02, 2021 03:27:41
    From Newsgroup: comp.sys.mac.system

    Thanks. Trying Usenapp now. But I use Usenet so infrequently now that it won't be worth paying for this app once the trial expires. Might have to stick with Google Groups. Ugh. Is there anything that runs on the command line like tin?


    On Jan 1, 2021 at 6:18:59 PM PST, "Savageduck" <savageduck1@removespam.me.com> wrote:

    On Jan 1, 2021 at 6:04:48 PM PST, "Gavin G" <ggrandish@gmail.com> wrote:

    What is everyone using M1 Macs using to read and post to Usenet now? I had >> been using tin in a Terminal window which I don't remember how I ever got >> installed; it was 10 years ago. I'm on Eternal September and don't need
    binaries.
    Thanks.

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>



    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Saturday, January 02, 2021 03:28:25
    From Newsgroup: comp.sys.mac.system

    In message <ruudnRupAvOORXLCnZ2dnUU7-KmdnZ2d@giganews.com> Savageduck <savageduck1@removespam.me.com> wrote:
    On Jan 1, 2021 at 6:04:48 PM PST, "Gavin G" <ggrandish@gmail.com> wrote:

    What is everyone using M1 Macs using to read and post to Usenet now? I had >> been using tin in a Terminal window which I don't remember how I ever got
    installed; it was 10 years ago. I'm on Eternal September and don't need
    binaries.
    Thanks.

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    slrn works perfectly on M1 machines.

    --
    You start a conversation you can't even finish it You're talkin' a
    lot, but you're not sayin' anything When I have nothing to say,
    my lips are sealed Say something once, why say it again?
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steve Carroll@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 01, 2021 20:44:11
    From Newsgroup: comp.sys.mac.system

    On Friday, January 1, 2021 at 7:19:06 PM UTC-7, Savageduck wrote:
    On Jan 1, 2021 at 6:04:48 PM PST, "Gavin G" <ggra...@gmail.com> wrote:

    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.
    Thanks.
    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>
    --
    Regards,
    Savageduck


    ChromeOS is based on Linux. Of course. Everyone is Peeler -- the oldest
    gag in the book.

    Taking effort educating yourself is never a waste. Asserting you know more than everyone else and attempting to persuade others that it is true, as Peeler tries to do? That is a waste. Of course I quoted examples of Peeler focusing on ego and not tech -- stating quotable lies, etc. His response:
    to change the topic.

    He is as incompetent as Peeler. Peeler can't get anything else to work, either.


    --
    Live on Kickstarter <https://www.spokeo.com/Dustin-Cook/Tennessee/Kingsport/p40064865906> https://redd.it/6sfkup
    Dustin Cook
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Krzysztof Mitko@invalid@kmitko.at.list.dot.pl to comp.sys.mac.system on Saturday, January 02, 2021 10:02:46
    From Newsgroup: comp.sys.mac.system

    Király wrote:

    Thanks. Trying Usenapp now. But I use Usenet so infrequently now that it won't
    be worth paying for this app once the trial expires. Might have to stick with Google Groups. Ugh. Is there anything that runs on the command line like tin?

    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    --
    Chemical engineers do it in packed beds.


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Joanna Shuttleworth@js@example.net to comp.sys.mac.system on Saturday, January 02, 2021 11:42:52
    From Newsgroup: comp.sys.mac.system

    On 2021-01-02, Lewis <g.kreme@kreme.dont-email.me> wrote:
    In message <ruudnRupAvOORXLCnZ2dnUU7-KmdnZ2d@giganews.com> Savageduck <savageduck1@removespam.me.com> wrote:
    On Jan 1, 2021 at 6:04:48 PM PST, "Gavin G" <ggrandish@gmail.com> wrote:

    What is everyone using M1 Macs using to read and post to Usenet now? I had >>> been using tin in a Terminal window which I don't remember how I ever got >>> installed; it was 10 years ago. I'm on Eternal September and don't need
    binaries.
    Thanks.

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    slrn works perfectly on M1 machines.


    yes it does
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Gavin G@ggrandish@gmail.com to comp.sys.mac.system on Saturday, January 02, 2021 07:18:16
    From Newsgroup: comp.sys.mac.system

    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote:
    Yes, tin :). You can install pre-compiled ARM binary via homebrew.
    Thanks for that. Got it installed. Of course it won't run, it needs configuration. Any good tutorials for dummies? Everything I can find is written for people who already know what they are doing. "When invoked as rtin or with the -r option, tin tries to connect to the NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER environment variable." I don't even know what "environment variable" means.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Saturday, January 02, 2021 10:37:33
    From Newsgroup: comp.sys.mac.system

    In article <cc57827e-45f3-4000-a35e-0b101fe1790dn@googlegroups.com>,
    Gavin G <ggrandish@gmail.com> wrote:

    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs configuration. Any good tutorials for dummies? Everything I can find is written for people who already know what they are doing. "When invoked as rtin or with the -r option, tin tries to connect to the NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER environment variable." I don't even know what "environment variable" means.

    then tin is not for you.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Gavin G@ggrandish@gmail.com to comp.sys.mac.system on Saturday, January 02, 2021 07:42:33
    From Newsgroup: comp.sys.mac.system

    On Saturday, January 2, 2021 at 7:37:37 AM UTC-8, nospam wrote:
    then tin is not for you.
    It has been for the 27 years that I've been using it. The last time I got tin installed on my Mac in 2010 was with help from the *good* folks here in c.s.m.s. If anyone can walk me through the steps or point me towards an easily understandable tutorial I'd appreciate it, thanks.
    K.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Saturday, January 02, 2021 10:48:35
    From Newsgroup: comp.sys.mac.system

    In article <da1760e3-98f6-4bda-b0cb-8bcc3b92fec2n@googlegroups.com>,
    Gavin G <ggrandish@gmail.com> wrote:

    It has been for the 27 years that I've been using it. The last time I got tin installed on my Mac in 2010 was with help from the *good* folks here in c.s.m.s. If anyone can walk me through the steps or point me towards an easily understandable tutorial I'd appreciate it, thanks.

    use the exact same steps.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Krzysztof Mitko@invalid@kmitko.at.list.dot.pl to comp.sys.mac.system on Saturday, January 02, 2021 16:20:19
    From Newsgroup: comp.sys.mac.system

    Gavin G wrote:

    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote:
    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs configuration.

    If you've used tin before, then you should have it already. Could you run
    these commands and paste the output?

    echo $SHELL
    ls -l ~/.tin/*
    alias
    echo $NNTPSERVER

    Any good tutorials for dummies? Everything I can find is written for people who already know what they are doing. "When invoked as rtin or with the -r option, tin tries to connect to the NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER environment variable." I don't even know what "environment variable" means.

    I don't know any tin tutorials, I haven't use it since mid-00s. Try to run it like this:

    NNTPSERVER=your.news.server tin

    The environment variables are just a set of strings being kept by your shell (e.g. bash, zsh, whateversh). Every time you launch a new program, it can
    check for the values of the variables and do something with them. You can set it as follows:

    export X=5
    (this means variable X will be equal to 5 entire time until you close the terminal tab)

    or

    X=5 somesoftware
    (this means X will be set just this one time you start somesoftware)

    --
    Chemical engineers do it in packed beds.


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Jolly Roger@jollyroger@pobox.com to comp.sys.mac.system on Saturday, January 02, 2021 18:00:07
    From Newsgroup: comp.sys.mac.system

    On 2021-01-02, Gavin G <ggrandish@gmail.com> wrote:
    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote:
    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs configuration. Any good tutorials for dummies? Everything I can find
    is written for people who already know what they are doing. "When
    invoked as rtin or with the -r option, tin tries to connect to the
    NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER environment variable." I don't even know what "environment variable"
    means.

    If have backups of the old computer where tin was installed and
    configured, you can just copy the config files over to the new system.

    --
    E-mail sent to this address may be devoured by my ravenous SPAM filter.
    I often ignore posts from Google. Use a real news client instead.

    JR
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Saturday, January 02, 2021 18:11:47
    From Newsgroup: comp.sys.mac.system

    In message <rsop7d$sf4$1@dont-email.me> Király <kiraly@spamsucks.ca> wrote:
    Thanks. Trying Usenapp now. But I use Usenet so infrequently now that it won't
    be worth paying for this app once the trial expires. Might have to stick with Google Groups. Ugh. Is there anything that runs on the command line like tin?

    Slrn.

    --
    All I know is that using the strap makes me feel like a hot woman in
    sunglasses. :-) ~jeffcarlson
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nmassello@nmassello@yahoo.com (Neill Massello) to comp.sys.mac.system on Saturday, January 02, 2021 15:12:59
    From Newsgroup: comp.sys.mac.system

    Savageduck <savageduck1@removespam.me.com> wrote:

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    AFAIK, only Usenapp runs native on Apple Silicon at the moment. Not that
    it matters that much: Rosetta 2 should be around for a while, at least
    through the next major version of macOS (12?).

    As for Hogwasher, it seems to have been in maintenance mode for the last
    few years. Not surprising, as there's little money to be made from
    Usenet client software.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From BungleBob@bunglebob@thejungle.com to comp.sys.mac.system on Sunday, January 03, 2021 12:29:04
    From Newsgroup: comp.sys.mac.system

    On 2021-01-02 22:12:59 +0000, Neill Massello said:
    Savageduck <savageduck1@removespam.me.com> wrote:

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    AFAIK, only Usenapp runs native on Apple Silicon at the moment. Not that
    it matters that much: Rosetta 2 should be around for a while, at least through the next major version of macOS (12?).

    The next version will be to be macOS 11.1. The name change to "11" was
    really only to mark the switch to Apple Silicon, otherwise it could
    have simply been macOS 10.16.

    macOS 12 won't be around for probably around 10 years or more ... if
    ever. Thanks to the iOS-ification of the Mac and macOS, and switch to
    Apple Silicon, there may not even be a "Mac" or "macOS" by then. :-(



    As for Hogwasher, it seems to have been in maintenance mode for the last
    few years. Not surprising, as there's little money to be made from
    Usenet client software.


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Saturday, January 02, 2021 18:37:23
    From Newsgroup: comp.sys.mac.system

    In article <rsqvju$kcb$1@gioia.aioe.org>, BungleBob
    <bunglebob@thejungle.com> wrote:

    The next version will be to be macOS 11.1.

    the *current* version is 11.1.

    The name change to "11" was
    really only to mark the switch to Apple Silicon, otherwise it could
    have simply been macOS 10.16.

    it was for developer versions.

    macOS 12 won't be around for probably around 10 years or more ... if
    ever. Thanks to the iOS-ification of the Mac and macOS, and switch to
    Apple Silicon, there may not even be a "Mac" or "macOS" by then. :-(

    try 10 months or so.

    mac os 12 is expected next fall, along with ios 15 and watchos 8.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Sunday, January 03, 2021 00:01:54
    From Newsgroup: comp.sys.mac.system

    In message <rsqvju$kcb$1@gioia.aioe.org> BungleBob <bunglebob@thejungle.com> wrote:
    On 2021-01-02 22:12:59 +0000, Neill Massello said:
    Savageduck <savageduck1@removespam.me.com> wrote:

    The two current M1 supported Usenet clients which are well supported are: >>>
    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    AFAIK, only Usenapp runs native on Apple Silicon at the moment. Not that
    it matters that much: Rosetta 2 should be around for a while, at least
    through the next major version of macOS (12?).

    The next version will be to be macOS 11.1.

    11.1 is the current version. 11.2 is currently in beta.

    macOS 12 won't be around for probably around 10 years or more

    Doubtful. October 2021 is more likely.

    --
    And sometimes there's a short cut. A door or a gate. Some standing
    stones. A tree cleft by lightning, a filing cabinet. Maybe just a
    spot on some moorland somewhere... A place where THERE is very
    nearly HERE... If some people knew where such a spot was, if they
    had experience of what happens when here and there become
    entangled, then they might - if they knew how - mark such a spot
    with certain stones. In the hope that enough daft buggers would
    take it as a warning and keep away. (Lords and Ladies)
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From STALKING_TARGET_13@frelwizzen@gmail.com to comp.sys.mac.system on Saturday, January 02, 2021 16:29:47
    From Newsgroup: comp.sys.mac.system

    On Saturday, January 2, 2021 at 5:01:57 PM UTC-7, Lewis wrote:
    In message <rsqvju$kcb$1...@gioia.aioe.org> BungleBob <bung...@thejungle.com> wrote:
    On 2021-01-02 22:12:59 +0000, Neill Massello said:
    Savageduck <savag...@removespam.me.com> wrote:

    The two current M1 supported Usenet clients which are well supported are:

    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    AFAIK, only Usenapp runs native on Apple Silicon at the moment. Not that >> it matters that much: Rosetta 2 should be around for a while, at least
    through the next major version of macOS (12?).

    The next version will be to be macOS 11.1.
    11.1 is the current version. 11.2 is currently in beta.
    macOS 12 won't be around for probably around 10 years or more
    Doubtful. October 2021 is more likely.

    --
    And sometimes there's a short cut. A door or a gate. Some standing
    stones. A tree cleft by lightning, a filing cabinet. Maybe just a
    spot on some moorland somewhere... A place where THERE is very
    nearly HERE... If some people knew where such a spot was, if they
    had experience of what happens when here and there become
    entangled, then they might - if they knew how - mark such a spot
    with certain stones. In the hope that enough daft buggers would
    take it as a warning and keep away. (Lords and Ladies)


    I usually go argument by argument unless someone has a history of really intense irrationality. With Peeler, I already understand what his goal
    is, all he dreams of is to harm J. J. Lodder and, unfortunately, he will
    do ANYTHING to get it. His never ending routine is to play 'easy mark'
    but reality shows it's all of his targets who are his suckers. Peeler-like advocates are now posting about the GNU/Linux "CLI" as if something like
    that actually is a goal of the community.

    Eventually, if you bother to focus... you would see that Peeler's plan
    is to 'accidentally' incite people and then play 'patsy. Of course, the
    top concern that matters to Peeler is being "accurate", and if he can not
    have that he will do whatever it takes to desperately kick advocates down, which only serves to disrupt threads.

    By following 'media talking heads' like that you get laws like 'culture
    wars'. Carried to its ultimate slippery slope, the push that it's 'unjust'
    for a traditional normal guy to not wish to identify as a dead body is
    born. Does J. J. Lodder believe the lies Peeler is pushing?


    --
    My Snoring Solution
    Automate Google Groups https://www.youtube.com/watch?v=hYQ4Tg0r0g0
    Dustin Cook the Fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Alan Browne@bitbucket@blackhole.com to comp.sys.mac.system on Monday, January 04, 2021 10:43:52
    From Newsgroup: comp.sys.mac.system

    On 2021-01-01 21:04, Gavin G wrote:
    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.

    Whatever 64b version that works on an intel machine should do fine on an
    Mx absent code re-compiled for the Mx.


    --
    "...there are many humorous things in this world; among them the white
    man's notion that he is less savage than the other savages."
    -Samuel Clemens
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From ant@ant@zimage.comANT (Ant) to comp.sys.mac.system on Monday, January 04, 2021 15:11:11
    From Newsgroup: comp.sys.mac.system

    Gavin G <ggrandish@gmail.com> wrote:
    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.
    Thanks.

    Tin package from brew or something? http://tin.org has its source code.
    --
    :) NY! Let's hope 2021 will be better.
    Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From ant@ant@zimage.comANT (Ant) to comp.sys.mac.system on Monday, January 04, 2021 15:12:10
    From Newsgroup: comp.sys.mac.system

    Jolly Roger <jollyroger@pobox.com> wrote:
    On 2021-01-02, Gavin G <ggrandish@gmail.com> wrote:
    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote:
    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs configuration. Any good tutorials for dummies? Everything I can find
    is written for people who already know what they are doing. "When
    invoked as rtin or with the -r option, tin tries to connect to the
    NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER environment variable." I don't even know what "environment variable"
    means.

    If have backups of the old computer where tin was installed and
    configured, you can just copy the config files over to the new system.

    Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
    code. Maybe brew has it?

    --
    :) NY! Let's hope 2021 will be better.
    Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From ant@ant@zimage.comANT (Ant) to comp.sys.mac.system on Monday, January 04, 2021 15:15:15
    From Newsgroup: comp.sys.mac.system

    Lewis <g.kreme@kreme.dont-email.me> wrote:
    In message <rsqvju$kcb$1@gioia.aioe.org> BungleBob <bunglebob@thejungle.com> wrote:
    On 2021-01-02 22:12:59 +0000, Neill Massello said:
    Savageduck <savageduck1@removespam.me.com> wrote:

    The two current M1 supported Usenet clients which are well supported are: >>>
    Usenapp
    <https://www.usenapp.com>

    ...and Hogwasher
    <https://www.asar.com/hogwasher.html>

    AFAIK, only Usenapp runs native on Apple Silicon at the moment. Not that >> it matters that much: Rosetta 2 should be around for a while, at least
    through the next major version of macOS (12?).

    The next version will be to be macOS 11.1.

    11.1 is the current version. 11.2 is currently in beta.

    macOS 12 won't be around for probably around 10 years or more

    Doubtful. October 2021 is more likely.

    Yeah. I think Apple dropped the idea to do major versions by .1 like in the past. Now, it's
    going 11, 12, 13, 14, etc.

    --
    :) NY! Let's hope 2021 will be better.
    Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Monday, January 04, 2021 22:07:19
    From Newsgroup: comp.sys.mac.system

    In message <FPSdnS-gCo83GW7CnZ2dnUU7-VGdnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:
    Jolly Roger <jollyroger@pobox.com> wrote:
    On 2021-01-02, Gavin G <ggrandish@gmail.com> wrote:
    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote: >> >> Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs
    configuration. Any good tutorials for dummies? Everything I can find
    is written for people who already know what they are doing. "When
    invoked as rtin or with the -r option, tin tries to connect to the
    NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER
    environment variable." I don't even know what "environment variable"
    means.

    If have backups of the old computer where tin was installed and
    configured, you can just copy the config files over to the new system.

    Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
    code. Maybe brew has it?

    $ brew search tin
    Formulae
    austin libpointing the_platinum_searcher tinysvm
    chart-testing libtins tin tinyxml
    git-integration nicotine-plus tinc tinyxml2
    git-interactive-rebase-tool osm2pgrouting tintin zsh-syntax-highlighting ✔
    gobject-introspection pgrouting tiny-fugue
    gsettings-desktop-schemas sidaf/pentest/inception tinycdb gst-editing-services skylighting tinyproxy
    Casks
    abricotine eclipse-testing prowritingaid syncsettings tinymediamanager
    asset-catalog-tinkerer gotomeeting retinizer teamviewermeeting tinypng4mac
    buildsettingextractor lighting ringcentral-meetings tencent-meeting unetbootin
    captin meetingbar scrutiny tinderbox valentina-studio
    clementine nightingale sentinel tinkerwell voov-meeting
    continuity-activation-tool porting-kit simplefloatingclock tiny-player webex-meetings

    I assume that tin and probably tinc and maybe tintin are related to the
    tin news client.


    Brew info would reveal more, but I don;t care enough to check as I am
    not going to be running tin (never have, rn trn nn, and slrn have been
    my clients).


    --
    My biggest problem is that Steve insists on serving PURPLE Kool Aid,
    an I don't like PURPLE <sip sip> Kool Aid.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Gavin G@ggrandish@gmail.com to comp.sys.mac.system on Monday, January 04, 2021 18:39:59
    From Newsgroup: comp.sys.mac.system

    On Monday, January 4, 2021 at 1:12:17 PM UTC-8, Ant wrote:
    Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
    code. Maybe brew has it?

    I copied my ~/.tin folder from my old Mac to my new one. It wasn't as easy as that.

    % ./tin -r
    Failed to connect to NNTP server.

    Looks like the command I had been running on my old Mac was:
    #!/bin/bash
    tin.dSYM -g news.eternal-september.org -A

    But that does nothing on the new Mac. Thanks for those who have helped so far.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Krzysztof Mitko@invalid@kmitko.at.list.dot.pl to comp.sys.mac.system on Tuesday, January 05, 2021 08:28:52
    From Newsgroup: comp.sys.mac.system

    Gavin G wrote:

    On Monday, January 4, 2021 at 1:12:17 PM UTC-8, Ant wrote:
    Yep, they're in ~/.tin. Just need to get a compiled tin binary.
    http://tin.org has its source
    code. Maybe brew has it?

    I copied my ~/.tin folder from my old Mac to my new one. It wasn't as easy as that.

    % ./tin -r
    Failed to connect to NNTP server.

    Looks like the command I had been running on my old Mac was:
    #!/bin/bash
    tin.dSYM -g news.eternal-september.org -A

    But that does nothing on the new Mac. Thanks for those who have helped so far.

    What happens if you run this?

    tin -g news.eternal-september.org -A

    --
    If you’re not part of the solution, you’re part of the precipitate.


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Tuesday, January 05, 2021 12:24:51
    From Newsgroup: comp.sys.mac.system

    On mar. 05 janvier 2021 (03:39),
    Gavin G <ggrandish@gmail.com> wrote:

    I copied my ~/.tin folder from my old Mac to my new one. It wasn't as
    easy as that.

    % ./tin -r
    Failed to connect to NNTP server.

    Looks like the command I had been running on my old Mac was:
    #!/bin/bash
    tin.dSYM -g news.eternal-september.org -A

    The "-r" switch makes tin reading news only from ${CONF_DIR}/nntpserver
    If that file doesn't exist, it fails.

    The "-g" switch looks for an alias defined in ${TIN_HOMEDIR:-"$HOME"}/.tin/newsrctable and overrides $NNTPSERVER

    Format of a newsrctable file:

    #v+
    # <nntp_server_hostname> <newsrc file> <alias for "-g"> news.eternal-september.org .newsrc-es es
    #v-

    As for the "-A" switch, it takes credentials from ${HOME}/.newsauth with
    the following format:

    #v+
    # <nntp_server_hostname> <password> <user>
    news.eternal-september.org my_password my_user
    #v-

    You may also check how tin has been compiled and allow reading via NNTP
    by issuing ` tin -V` (which produces the following):

    #v+
    tin -V
    Version : tin 2.4.4 release 20191224 ("Millburn") Nov 8 2020 09:14:11 Platform:
    OS-Name = "freebsd11.4"
    Compiler:
    CC = "cc"
    CPP = "cpp"
    CPPFLAGS = "-I/usr/local/include -DLIBICONV_PLUG -DNNTP_SERVER_FILE=\"/usr/local/etc/nntpserver\" -DLIBICONV_PLUG -D_XOPEN_SOURCE_EXTENDED"
    Linker and Libraries:
    LD = "cc"
    LDFLAGS = " -L/usr/local/lib -fstack-protector-strong "
    LIBS = "-lpcre -lncursesw -luu -licuuc "
    PCRE = "8.44 2020-02-12"
    Characteristics:
    -DEBUG *+NNTP_ONLY* -NO_POSTING -BROKEN_LISTGROUP +XHDR_XREF
    -HAVE_FASCIST_NEWSADMIN +ENABLE_IPV6 +HAVE_COREFILE
    -NO_SHELL_ESCAPE -DISABLE_PRINTING -DONT_HAVE_PIPING -NO_ETIQUETTE
    +HAVE_LONG_FILE_NAMES +APPEND_PID -HAVE_MH_MAIL_HANDLING
    +HAVE_ISPELL +HAVE_METAMAIL +HAVE_SUM
    +HAVE_COLOR -HAVE_PGP -HAVE_PGPK +HAVE_GPG
    +MIME_BREAK_LONG_LINES +MIME_STRICT_CHARSET +CHARSET_CONVERSION
    +MULTIBYTE_ABLE -NO_LOCALE -USE_LONG_ARTICLE_NUMBERS
    -USE_CANLOCK -EVIL_INSIDE -FORGERY -TINC_DNS -ENFORCE_RFC1034
    -REQUIRE_BRACKETS_IN_DOMAIN_LITERAL -ALLOW_FWS_IN_NEWSGROUPLIST
    #v-

    To summarize, either start tin(1) with:

    #v+
    # Without ${CONF_DIR}/nntpserver, $NNTPSERVER is set and
    # ${HOME}/.newsauth does have credentials for the server which
    # requires authentication:
    tin -r -A

    # Without $NNTPSERVER set, overriding ${CONF_DIR}/nntpserver,
    # ${HOME}/.tin/newsrctable does have an alias defined for an NNTP
    # server when using "-g" switch and ${HOME}/.newsauth does have
    # credentials for the server which requires authentication:
    tin -r -A -g <alias>
    #v-

    Bear in mind that you have to know basic understanding of how shell
    works for using tin as all is done on a shell.

    hth

    --
    echo 'zngg@yi426.rh' | \
    tr '[a-z]' '[n-za-m]'
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steve Carroll@frelwizzen@gmail.com to comp.sys.mac.system on Tuesday, January 05, 2021 04:58:30
    From Newsgroup: comp.sys.mac.system

    On Monday, January 4, 2021 at 3:07:22 PM UTC-7, Lewis wrote:
    In message <FPSdnS-gCo83GW7C...@earthlink.com> Ant <a...@zimage.comANT> wrote:
    Jolly Roger <jolly...@pobox.com> wrote:
    On 2021-01-02, Gavin G <ggra...@gmail.com> wrote:
    On Saturday, January 2, 2021 at 2:02:49 AM UTC-8, Krzysztof Mitko wrote:
    Yes, tin :). You can install pre-compiled ARM binary via homebrew.

    Thanks for that. Got it installed. Of course it won't run, it needs
    configuration. Any good tutorials for dummies? Everything I can find
    is written for people who already know what they are doing. "When
    invoked as rtin or with the -r option, tin tries to connect to the
    NNTP server specified in the file /etc/nntpserver or in the NNTPSERVER >> > environment variable." I don't even know what "environment variable"
    means.

    If have backups of the old computer where tin was installed and
    configured, you can just copy the config files over to the new system.

    Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
    code. Maybe brew has it?
    $ brew search tin
    Formulae
    austin libpointing the_platinum_searcher tinysvm
    chart-testing libtins tin tinyxml
    git-integration nicotine-plus tinc tinyxml2
    git-interactive-rebase-tool osm2pgrouting tintin zsh-syntax-highlighting ✔ gobject-introspection pgrouting tiny-fugue
    gsettings-desktop-schemas sidaf/pentest/inception tinycdb gst-editing-services skylighting tinyproxy
    Casks
    abricotine eclipse-testing prowritingaid syncsettings tinymediamanager asset-catalog-tinkerer gotomeeting retinizer teamviewermeeting tinypng4mac buildsettingextractor lighting ringcentral-meetings tencent-meeting unetbootin
    captin meetingbar scrutiny tinderbox valentina-studio
    clementine nightingale sentinel tinkerwell voov-meeting continuity-activation-tool porting-kit simplefloatingclock tiny-player webex-meetings

    I assume that tin and probably tinc and maybe tintin are related to the
    tin news client.


    Brew info would reveal more, but I don;t care enough to check as I am
    not going to be running tin (never have, rn trn nn, and slrn have been
    my clients).


    --
    My biggest problem is that Steve insists on serving PURPLE Kool Aid,
    an I don't like PURPLE <sip sip> Kool Aid.
    Too many individuals keep responding to Mike Easter. Frankly I do not indict Shadow for his ire but I can not fathom why he comes here at all. Shadow
    is far more interested in dialog as is common in a Facebook forum and trolling environments just will never work for him. You are quick as a tuna on ice. Sadly this is what happens when acutely inferior self esteem takes over
    Mike Easter's every moment. Thus, my unedited statement stands literal and correct. All that Mike Easter cares about is that Mike Easter gets to deliver his poorly written flyer and then hang up and giggle about it. The fact
    that Shadow is a real person on the other end of the phone is what gets
    him off.
    -
    What Every Entrepreneur Must Know <http://web.archive.org/web/20200911090855/https://www.usphonebook.com/423- 491-1448?Dustin-Cook=&Diesel=&Gremlin=> <https://alt.computer.workshop.narkive.com/dCDisEHZ/dustin-cook-aka-diesel- aka-gremlin-i-fucked-you-over-with-your-bank-account>
    Dustin Cook the functionally illiterate fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Stephen Carroll@frelwizzen@gmail.com to comp.sys.mac.system on Tuesday, January 05, 2021 12:53:14
    From Newsgroup: comp.sys.mac.system

    On Monday, January 4, 2021 at 7:40:02 PM UTC-7, ggra...@gmail.com wrote:
    On Monday, January 4, 2021 at 1:12:17 PM UTC-8, Ant wrote:
    Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
    code. Maybe brew has it?
    I copied my ~/.tin folder from my old Mac to my new one. It wasn't as easy as that.

    % ./tin -r
    Failed to connect to NNTP server.

    Looks like the command I had been running on my old Mac was:
    #!/bin/bash
    tin.dSYM -g news.eternal-september.org -A

    But that does nothing on the new Mac. Thanks for those who have helped so far.


    All joking aside, what lie?

    I bet we have different perspectives for a good reason. Turns out Jeff
    Relf's constant mentioning of Ian McCall met that definition, so he accused Ian McCall of making that up.

    If Jeff Relf calls getting his ass kicked hard left and right day in and
    day out by everyone good 'trolling', then sure... he is a first-class troll.
    I can't personally agree with that definition, I use another term. I call
    that person an out-and-out halfwit. It was Jeff Relf who was publicly asking how better to improve his forgeries. Usenet is a world-wide non-organization based on virtue that Jeff Relf lacks.


    --
    What Every Entrepreneur Must Know <https://www.whitepages.com/phone/1-423-491-1448>
    Dustin Cook the Fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (Kir?ly) to comp.sys.mac.system on Wednesday, January 06, 2021 17:20:30
    From Newsgroup: comp.sys.mac.system

    Alan Browne <bitbucket@blackhole.com> wrote:
    On 2021-01-01 21:04, Gavin G wrote:
    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.

    Whatever 64b version that works on an intel machine should do fine on an
    Mx absent code re-compiled for the Mx.

    Thanks folks. I got it working and am posting from tin now. I just
    copied all of the files from my old Intel Mac to my new M1 Mac. It took
    me a while to find them all. Some were in /usr/local/bin, some were in
    ~, and one was in /etc (had to make a tin folder there and add the
    file).

    I am surprised it worked. When I moved from PowerPC to Intel this did
    not work and I needed to compile a new tin binary. So I never expected
    using a 10-year old binary would work this time. But it did.

    --
    K.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From ant@ant@zimage.comANT (Ant) to comp.sys.mac.system on Wednesday, January 06, 2021 16:38:26
    From Newsgroup: comp.sys.mac.system

    Kir?ly <me@home.spamsucks.ca> wrote:
    Alan Browne <bitbucket@blackhole.com> wrote:
    On 2021-01-01 21:04, Gavin G wrote:
    What is everyone using M1 Macs using to read and post to Usenet now? I had been using tin in a Terminal window which I don't remember how I ever got installed; it was 10 years ago. I'm on Eternal September and don't need binaries.

    Whatever 64b version that works on an intel machine should do fine on an Mx absent code re-compiled for the Mx.

    Thanks folks. I got it working and am posting from tin now. I just
    copied all of the files from my old Intel Mac to my new M1 Mac. It took
    me a while to find them all. Some were in /usr/local/bin, some were in
    ~, and one was in /etc (had to make a tin folder there and add the
    file).

    I am surprised it worked. When I moved from PowerPC to Intel this did
    not work and I needed to compile a new tin binary. So I never expected
    using a 10-year old binary would work this time. But it did.

    Wow, it works? Amazing. What version is it?
    --
    :) NY! Let's hope 2021 will be better.
    Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (Kir?ly) to comp.sys.mac.system on Thursday, January 07, 2021 02:31:08
    From Newsgroup: comp.sys.mac.system


    Ant <ant@zimage.comant> wrote:
    Wow, it works? Amazing. What version is it?

    It's tin 1.9.6, released in November of 2010. I still need to dig down
    the memory hole and remember how I fixed the text encoding, since I have
    again lost the accented "a" in my name, which I remember struggling to
    fix last time too.

    --
    K.

    Lang may your lum reek.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Wednesday, January 06, 2021 21:34:58
    From Newsgroup: comp.sys.mac.system

    In article <rt5rpc$t7g$1@dont-email.me>, Kir?ly <me@home.spamsucks.ca>
    wrote:

    It's tin 1.9.6, released in November of 2010

    might want to update that.

    <http://www.tin.org>
    Announcement: TIN 2.4.5 (stable) was released on December 24, 2020
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Thursday, January 07, 2021 04:17:18
    From Newsgroup: comp.sys.mac.system

    nospam <nospam@nospam.invalid> wrote:
    It's tin 1.9.6, released in November of 2010

    might want to update that.

    <http://www.tin.org>
    Announcement: TIN 2.4.5 (stable) was released on December 24, 2020

    Haha good one. :)
    I mentioned already that I can't compile those from scratch without
    help. So unless someone wants walk me through all of the steps that
    produces something that actually works, I'll just keep using what I
    have, which continues to work just fine.

    --
    K.

    Lang may your lum reek.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Thursday, January 07, 2021 00:45:59
    From Newsgroup: comp.sys.mac.system

    In article <rt620e$urr$1@dont-email.me>, Kirly <me@home.spamsucks.ca>
    wrote:

    It's tin 1.9.6, released in November of 2010

    might want to update that.

    <http://www.tin.org>
    Announcement: TIN 2.4.5 (stable) was released on December 24, 2020

    Haha good one. :)
    I mentioned already that I can't compile those from scratch without
    help. So unless someone wants walk me through all of the steps that
    produces something that actually works, I'll just keep using what I
    have, which continues to work just fine.

    download it and review the steps in the readme and readme.mac files.

    note that the mac readme suggests macports or fink as an alternative to compiling it from scratch.

    post about anything that doesn't work as expected.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From BungleBob@bunglebob@thejungle.com to comp.sys.mac.system on Thursday, January 07, 2021 19:09:39
    From Newsgroup: comp.sys.mac.system

    On 2021-01-07 02:31:08 +0000, Kir?ly said:
    Ant <ant@zimage.comant> wrote:

    Wow, it works? Amazing. What version is it?

    It's tin 1.9.6, released in November of 2010. I still need to dig down
    the memory hole and remember how I fixed the text encoding, since I have again lost the accented "a" in my name, which I remember struggling to
    fix last time too.

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Krzysztof Mitko@invalid@kmitko.at.list.dot.pl to comp.sys.mac.system on Thursday, January 07, 2021 08:33:43
    From Newsgroup: comp.sys.mac.system

    BungleBob wrote:

    On 2021-01-07 02:31:08 +0000, Kir?ly said:
    Ant <ant@zimage.comant> wrote:

    Wow, it works? Amazing. What version is it?

    It's tin 1.9.6, released in November of 2010. I still need to dig down
    the memory hole and remember how I fixed the text encoding, since I have
    again lost the accented "a" in my name, which I remember struggling to
    fix last time too.

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.

    Nope. “Plain text” ≠ ASCII 🙂.

    --
    Je suis Marxiste, tendance Groucho.


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Thursday, January 07, 2021 03:51:57
    From Newsgroup: comp.sys.mac.system

    In article <rt68j3$p10$1@gioia.aioe.org>, BungleBob
    <bunglebob@thejungle.com> wrote:

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.

    yes it should, which is why usenet has supported unicode for many years.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Thursday, January 07, 2021 09:44:03
    From Newsgroup: comp.sys.mac.system

    On jeu. 07 janvier 2021 (05:17),
    Király <me@home.spamsucks.ca> wrote:

    Haha good one. :)
    I mentioned already that I can't compile those from scratch without
    help. So unless someone wants walk me through all of the steps that
    produces something that actually works, I'll just keep using what I
    have, which continues to work just fine.

    As nospam stated, compiling tin on Darwin/Mac OS X shouldn't be a
    problem, even on Big Sur.

    By the time I wrote down README.MAC, informations are still valid
    through High Sierra (haven't planned to use anything above as I moved
    away from Mac OS X). But you can update that file and submit it to Urs
    Janßen which is current tin's maintainer.

    If compiling stuff isn't easy for you, install tin from a package
    manager (MacPorts, homebrew, Fink, pkgsrc, etc.) or ask someone to make
    a pkg installer (through I wouldn't recommend it due to security risks
    if you don't trust the one who's making that pkg).

    --
    <moupio>J'ai l'impression que t'en a rien a foutre quand je parle
    <Jerome>ok
    <moupio>...
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Thursday, January 07, 2021 18:54:11
    From Newsgroup: comp.sys.mac.system

    In message <rt68j3$p10$1@gioia.aioe.org> BungleBob <bunglebob@thejungle.com> wrote:
    On 2021-01-07 02:31:08 +0000, Kir?ly said:
    Ant <ant@zimage.comant> wrote:

    Wow, it works? Amazing. What version is it?

    It's tin 1.9.6, released in November of 2010. I still need to dig down
    the memory hole and remember how I fixed the text encoding, since I have
    again lost the accented "a" in my name, which I remember struggling to
    fix last time too.

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.

    Accented characters (and the entirety of UTF-8) *are* plain text.

    --
    The quality of our thoughts and ideas can only be as good as the
    quality of our language.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Friday, January 08, 2021 05:32:56
    From Newsgroup: comp.sys.mac.system

    nospam <nospam@nospam.invalid> wrote:
    download it and review the steps in the readme and readme.mac files.

    note that the mac readme suggests macports or fink as an alternative to compiling it from scratch.

    post about anything that doesn't work as expected.

    I tried running again the tin binary I downloaded from homebrew, with
    the command ./tin -g news.eternal-september.org -A, and it works with
    all of my config files now in place. But it's using the vi editor to
    compose, a fearsome editor if I ever saw one. How do I tell it to use
    nano? I remember this is a preference I hard-coded into my home-compiled binary last time.

    The man page says this:
    Invocation of your editor (editor_format)
    The format string used to create the editor start command
    with parameters. Default is
    "%E +%N %F" (i.e., /bin/vi +7 .article).

    I have no idea what that means.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Friday, January 08, 2021 12:08:06
    From Newsgroup: comp.sys.mac.system

    On ven. 08 janvier 2021 (06:32),
    Király <me@home.spamsucks.ca> wrote:

    I tried running again the tin binary I downloaded from homebrew, with
    the command ./tin -g news.eternal-september.org -A, and it works with
    all of my config files now in place. But it's using the vi editor to compose, a fearsome editor if I ever saw one. How do I tell it to use
    nano? I remember this is a preference I hard-coded into my home-compiled binary last time.

    vi(m) isn't as scary as ed(1) ;)

    The man page says this:
    Invocation of your editor (editor_format)
    The format string used to create the editor start command
    with parameters. Default is
    "%E +%N %F" (i.e., /bin/vi +7 .article).

    I have no idea what that means.

    Then change it either within tin's menu or directly on your ~/.tin/tinrc
    For using nano (check nano's path on your system). The following
    instructs nano:
    - to wrap text lines to 72 characters (-r 72);
    - to convert tabs to spaces (-E);
    - to set tabs to 4 (-T 4);
    - to detect word boundaries differently by treating punctuation
    characters as part of a word (-W);
    - to automatically hard-wrap the current line when it becomes overlong
    (-b);
    - to constantly show the cursor position on the status bar (-c);
    - to save a changed buffer without prompting (-t);
    - to specify the name of the syntax highlighting to use from among the
    ones defined in the nanorc files (-Y).

    #v+
    editor_format=/usr/local/bin/nano -EWbct -r 72 -T 4 -Y tin +%N %F
    #v-

    %N: tin's variable piped to your editor;
    %F: tin's variable piped to your editor;
    %E: editor by default explicity sets at compilation time or when $EDITOR shell's environement variable is set.

    hth

    --
    <Marek62> Mais des fois j'suis chiant et con
    <Stev'> On a tous un côté féminin
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From STALKING_TARGET_47@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 05:34:54
    From Newsgroup: comp.sys.mac.system

    On Thursday, January 7, 2021 at 1:52:01 AM UTC-7, nospam wrote:
    In article <rt68j3$p10$1...@gioia.aioe.org>, BungleBob <bung...@thejungle.com> wrote:

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.
    yes it should, which is why usenet has supported unicode for many years.


    I know the flooder is F. Russell, who is a programmer but I don't know
    if it could be used to get by Google's spam filters.

    Marketing is a wonderful thing and consumer herd mentality is even better. "Somewhere between 1996 or 2002 I trusted Shadow - the fully laughable
    liar" - F. Russell.

    Now why the task to time a script via usenet in an embedded system?
    Of course, he didn't initially list this as part of his, predictably, self-serving 'specification' <shrug>. So he changed his story to responding
    to him. It is easy as pie to cherrypick by focusing on a small number
    of isolated examples clashing from what is typical. What a better tactic
    from an advocacy outlook are the expected circumstances. What I understand
    is, if I've talked to people calling themselves "Socialists" while sky
    diving, they were not the usual F. Russell class that likes to cry about everything. Why are such folks clearly never content... WTF is up with
    that?


    -
    Eight things to never feed your dog!
    https://youtu.be/hYQ4Tg0r0g0
    Automate Google Groups https://www.youtube.com/watch?v=hYQ4Tg0r0g0&feature=youtu.be
    https://duckduckgo.com/?q=Dustin+Cook+the+functionally+illiterate+fraud
    Dustin Cook
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Friday, January 08, 2021 14:39:04
    From Newsgroup: comp.sys.mac.system

    Matt <matt@lv426.eu.invalid> wrote:

    Then change it either within tin's menu or directly on your ~/.tin/tinrc
    For using nano (check nano's path on your system).

    I couldn't find a setting in tin's menu to specify the editor. I tried
    pasting this into my tinrc file:

    #v+
    editor_format=/usr/bin/nano -EWbct -r 72 -T 4 -Y tin +%N %F
    #v-

    ...but it didn't do anything. tin is still using vi to compose.
    Google and the tin man page aren't helping me. Any other ideas?

    Thanks
    K
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Stefen Carroll - fretwizer@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 07:09:27
    From Newsgroup: comp.sys.mac.system

    On Thursday, January 7, 2021 at 11:54:14 AM UTC-7, Lewis wrote:
    In message <rt68j3$p10$1...@gioia.aioe.org> BungleBob <bung...@thejungle.com> wrote:
    On 2021-01-07 02:31:08 +0000, Kir?ly said:
    Ant <a...@zimage.comant> wrote:

    Wow, it works? Amazing. What version is it?

    It's tin 1.9.6, released in November of 2010. I still need to dig down
    the memory hole and remember how I fixed the text encoding, since I have >> again lost the accented "a" in my name, which I remember struggling to
    fix last time too.

    USENET is meant to be plain text, so that shouldn't include accented characters anyway.
    Accented characters (and the entirety of UTF-8) *are* plain text.

    --
    The quality of our thoughts and ideas can only be as good as the
    quality of our language.


    I can not tolerate that. Dumbness is dumbness and there are all kinds of people who are of one mind with it. Too many are even teachers. And in reply you have nothing but a crack to start more flooding.

    Why would J. J. Lodder need 'helpers'? He is the one who provides facts
    for his side of the "debates". With no proof at all, as is expected for Shadow.


    --
    My Snoring Solution https://duckduckgo.com/?q=Dustin+Cook%3A+functionally+illiterate+fraud https://www.google.com/search?q=Dustin%20Cook%20functionally%20illiterate%20fraud
    Dustin Cook the Fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steven Carroll - fretwizen@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 08:43:20
    From Newsgroup: comp.sys.mac.system

    On Thursday, January 7, 2021 at 10:32:59 PM UTC-7, Király wrote:
    nospam <nos...@nospam.invalid> wrote:
    download it and review the steps in the readme and readme.mac files.

    note that the mac readme suggests macports or fink as an alternative to compiling it from scratch.

    post about anything that doesn't work as expected.
    I tried running again the tin binary I downloaded from homebrew, with
    the command ./tin -g news.eternal-september.org -A, and it works with
    all of my config files now in place. But it's using the vi editor to compose, a fearsome editor if I ever saw one. How do I tell it to use
    nano? I remember this is a preference I hard-coded into my home-compiled binary last time.

    The man page says this:
    Invocation of your editor (editor_format)
    The format string used to create the editor start command
    with parameters. Default is
    "%E +%N %F" (i.e., /bin/vi +7 .article).

    I have no idea what that means.
    It's like a prank call. Kelly Phillips has already decided what he is going
    to say before he calls. What you say is irrelevant. What Theo says is ignored. I just use a KF and won't see the flooding. Kelly Phillips's crap has made
    an utter mess of cola via GG, so I don't even try trolling anything with
    my client anymore. One thing he has done with this nonsense is that the
    Kelly Phillips boycott has been shown to clearly be the right thing.
    It's Kelly Phillips's problem but he does not care. Obviously he would
    rather blame others than face reality.
    Kelly Phillips writes all kinds of hogwash, don't use that idiot as a reference.
    ClamX was initially written and back linked using a bootleg copy of visual studio, in assembly.
    --
    This Trick Gets Women Hot For You!! https://swisscows.com/web?query=dustin%20cook%20%22functionally%20illiterate%20fraud%22
    https://www.bing.com/search?q=Dustin%20Cook%20functionally%20illiterate%20fraud Dustin Cook is a functionally illiterate fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From bje@bje@ripco.com to comp.sys.mac.system on Friday, January 08, 2021 17:01:15
    From Newsgroup: comp.sys.mac.system

    Kir?ly <me@home.spamsucks.ca> wrote:

    ...but it didn't do anything. tin is still using vi to compose.
    Google and the tin man page aren't helping me. Any other ideas?


    Tin mostly relies on environmental variables.

    Using terminal, while in your home directory...

    pico .bash_profile

    that will create a new file (in your home dir) called .bash_profile.

    Stick in these two lines:

    export EDITOR=/usr/bin/pico
    export VISUAL=/usr/bin/pico

    if you want to avoid typing in the nntpserver all the time:

    export NNTPSERVER=your.news.server.com

    then save the file (exit pico), exit out of the terminal and re-open.

    Then try this:

    tin -r -A

    and post a message in a test group to make sure pico comes up.

    You can check your work with .bash_profile by this (in terminal):

    env

    The NNTPSERVER, EDITOR and VISUAL should be listed there.

    -bruce
    bje@ripco.com

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steven Carroll - fretwizen@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 10:03:31
    From Newsgroup: comp.sys.mac.system

    On Friday, January 8, 2021 at 10:01:19 AM UTC-7, b...@ripco.com wrote:
    Kir?ly <m...@home.spamsucks.ca> wrote:

    ...but it didn't do anything. tin is still using vi to compose.
    Google and the tin man page aren't helping me. Any other ideas?
    Tin mostly relies on environmental variables.

    Using terminal, while in your home directory...

    pico .bash_profile

    that will create a new file (in your home dir) called .bash_profile.

    Stick in these two lines:

    export EDITOR=/usr/bin/pico
    export VISUAL=/usr/bin/pico

    if you want to avoid typing in the nntpserver all the time:

    export NNTPSERVER=your.news.server.com

    then save the file (exit pico), exit out of the terminal and re-open.

    Then try this:

    tin -r -A

    and post a message in a test group to make sure pico comes up.

    You can check your work with .bash_profile by this (in terminal):

    env

    The NNTPSERVER, EDITOR and VISUAL should be listed there.

    -bruce
    b...@ripco.com


    Was that meant to be to Jeff Relf?

    Jeff Relf has gone the extra mile, essentially hand holding Tattoo Vampire
    on coding practices only for Tattoo Vampire to blindly attack him and
    continue to show that he has no real interest in the subject. In all reality, it's too hard for snit. So he changed his story to talking about his family.

    Tattoo Vampire pretends that he uses Linux, while really he never used
    it on anything but an emulator and honesty used it.

    Jeff Relf must have read the Tattoo Vampire signature lines and became
    acutely resentful. I suspect this is not our first demonstration of the improved Jeff Relf. All joking aside, those of you who troll are not able
    to control Jeff Relf anymore.

    For all the gloating Tattoo Vampire's done on this topic, the 'Information Architect' does not know how to do this. It literally takes a couple seconds to highlight a range and 'sign' it.

    -
    Do not click this link!!! https://search.givewater.com/serp?q=Dustin+Cook+%22functionally+illiterate+fraud%22
    <https://findwhocallsyou.com/4234911448?CallerInfo>
    Dustin Cook: Functionally Illiterate Fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Saturday, January 09, 2021 02:02:28
    From Newsgroup: comp.sys.mac.system

    On ven. 08 janvier 2021 (15:39),
    Király <me@home.spamsucks.ca> wrote:

    I couldn't find a setting in tin's menu to specify the editor. I tried pasting this into my tinrc file:

    #v+
    editor_format=/usr/bin/nano -EWbct -r 72 -T 4 -Y tin +%N %F
    #v-

    ...but it didn't do anything. tin is still using vi to compose.
    Google and the tin man page aren't helping me. Any other ideas?

    Thanks
    K

    Editor's menu option would be in newer release than 1.9.6 (can't recall
    when it was introduced). Actually in 2.x that option is at position 129
    in tin's menu.

    As Bruce saids, tin relies a lot on your shell environment and has
    precedence over defined configurations through rc files, though my
    $EDITOR and $VISUAL are set to vim(1) whereas I'm using nano(1) "on"
    tin.

    Also please note that ~/.tin/tinrc is read at startup time so you may
    have to relaunch tin. You can ditch too the "-Y tin" which can prevent
    tin to launch your editor if you don't have any ~/.tin/*.nanorc

    Another thing to check is you might have a global tinrc lying on ${TIN_LIBDIR:-NEWSLIBDIR}/tinrc and/or /etc/tin/tin.defaults which take precedence over user's one.

    All of tin's configuration is located in tin's section 5 manpage which
    can be accessed with `man 5 tin`.

    hth

    --
    <algeriano> slt mon ANGE imagine qu'on est toi et moi seule ds un
    appartement. tu va me faire quoi?
    <Ninou> je te cours après avec une pelle ?
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Saturday, January 09, 2021 02:23:05
    From Newsgroup: comp.sys.mac.system

    bje@ripco.com wrote:
    pico .bash_profile

    that will create a new file (in your home dir) called .bash_profile.

    Stick in these two lines:

    export EDITOR=/usr/bin/pico
    export VISUAL=/usr/bin/pico

    Thanks, I tried that, but bash seems to have ignored it; tin is still
    using vi as its editor.

    You can check your work with .bash_profile by this (in terminal):

    env

    The NNTPSERVER, EDITOR and VISUAL should be listed there.

    They aren't.

    : kiraly@Our-Mac-Mini ~ % bash
    :
    : The default interactive shell is now zsh.
    : To update your account to use zsh, please run `chsh -s /bin/zsh`.
    : For more details, please visit https://support.apple.com/kb/HT208050.
    : bash-3.2$ env
    : TERM_PROGRAM=Apple_Terminal
    : SHELL=/bin/zsh
    : TERM=xterm-256color
    : [etc]

    It returns a whole bunch of stuff that have nothing to do with my .bash_profile file. What is the proper file to add those nano editor
    settings to?

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Saturday, January 09, 2021 02:37:41
    From Newsgroup: comp.sys.mac.system

    Matt <matt@lv426.eu.invalid> wrote:
    Editor's menu option would be in newer release than 1.9.6 (can't recall
    when it was introduced). Actually in 2.x that option is at position 129
    in tin's menu.

    My tin 2.4.5 menu doesn't have that option, the last menu item is in
    positon 123.

    As Bruce saids, tin relies a lot on your shell environment and has precedence over defined configurations through rc files, though my
    $EDITOR and $VISUAL are set to vim(1) whereas I'm using nano(1) "on"
    tin.

    Also please note that ~/.tin/tinrc is read at startup time so you may
    have to relaunch tin. You can ditch too the "-Y tin" which can prevent
    tin to launch your editor if you don't have any ~/.tin/*.nanorc

    Another thing to check is you might have a global tinrc lying on ${TIN_LIBDIR:-NEWSLIBDIR}/tinrc and/or /etc/tin/tin.defaults which take precedence over user's one.

    My head is spinning reading all of that. I'm just going to stick with my 10-year old version, tin 1.9.6. It uses the editor that I want and just
    works. I didn't find anything that 2.4.5 does better or even differently anyway.

    Many thanks for all the help everyone.

    --
    K.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steven - fretwizzer 3765@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 20:17:21
    From Newsgroup: comp.sys.mac.system

    On Friday, January 8, 2021 at 7:23:08 PM UTC-7, Király wrote:
    b...@ripco.com wrote:
    pico .bash_profile

    that will create a new file (in your home dir) called .bash_profile.

    Stick in these two lines:

    export EDITOR=/usr/bin/pico
    export VISUAL=/usr/bin/pico
    Thanks, I tried that, but bash seems to have ignored it; tin is still
    using vi as its editor.
    You can check your work with .bash_profile by this (in terminal):

    env

    The NNTPSERVER, EDITOR and VISUAL should be listed there.
    They aren't.

    : kiraly@Our-Mac-Mini ~ % bash
    :
    : The default interactive shell is now zsh.
    : To update your account to use zsh, please run `chsh -s /bin/zsh`.
    : For more details, please visit https://support.apple.com/kb/HT208050.
    : bash-3.2$ env
    : TERM_PROGRAM=Apple_Terminal
    : SHELL=/bin/zsh
    : TERM=xterm-256color
    : [etc]

    It returns a whole bunch of stuff that have nothing to do with my .bash_profile file. What is the proper file to add those nano editor settings to?
    The most obvious answer: Snit's Bitch David Brooks's consumed recreational drugs since then, and 'disremembered'.
    He disturbs an entire group of people who have nothing to do with anything, but that's a narcissist for you. What Theo and I care about isn't a factor. Snit's Bitch David Brooks and Theo both lie ceaselessly and outrageously
    and continue to do so. So no sense in showing any further respect or judiciousness.
    --
    One Smart Penny <https://www.truepeoplesearch.com/results?name=4234911448&Diesel&Gremlin&Dustin_Cook>
    https://gibiru.com/results.html?q=Dustin+Cook+%22functionally+illiterate+fraud%22
    Dustin Cook the functionally illiterate fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steven - fretwizzer 3765@frelwizzen@gmail.com to comp.sys.mac.system on Friday, January 08, 2021 23:57:53
    From Newsgroup: comp.sys.mac.system

    On Friday, January 8, 2021 at 11:03:34 AM UTC-7, Steven - fretwizzer 3765 wrote:
    On Friday, January 8, 2021 at 10:01:19 AM UTC-7, b...@ripco.com wrote:
    Kir?ly <m...@home.spamsucks.ca> wrote:

    ...but it didn't do anything. tin is still using vi to compose.
    Google and the tin man page aren't helping me. Any other ideas?
    Tin mostly relies on environmental variables.

    Using terminal, while in your home directory...

    pico .bash_profile

    that will create a new file (in your home dir) called .bash_profile.

    Stick in these two lines:

    export EDITOR=/usr/bin/pico
    export VISUAL=/usr/bin/pico

    if you want to avoid typing in the nntpserver all the time:

    export NNTPSERVER=your.news.server.com

    then save the file (exit pico), exit out of the terminal and re-open.

    Then try this:

    tin -r -A

    and post a message in a test group to make sure pico comes up.

    You can check your work with .bash_profile by this (in terminal):

    env

    The NNTPSERVER, EDITOR and VISUAL should be listed there.

    -bruce
    b...@ripco.com
    Was that meant to be to Jeff Relf?

    Jeff Relf has gone the extra mile, essentially hand holding Tattoo Vampire on coding practices only for Tattoo Vampire to blindly attack him and continue to show that he has no real interest in the subject. In all reality,
    it's too hard for snit. So he changed his story to talking about his family.

    Tattoo Vampire pretends that he uses Linux, while really he never used
    it on anything but an emulator and honesty used it.

    Jeff Relf must have read the Tattoo Vampire signature lines and became acutely resentful. I suspect this is not our first demonstration of the improved Jeff Relf. All joking aside, those of you who troll are not able
    to control Jeff Relf anymore.

    For all the gloating Tattoo Vampire's done on this topic, the 'Information Architect' does not know how to do this. It literally takes a couple seconds to highlight a range and 'sign' it.

    -
    Do not click this link!!! https://search.givewater.com/serp?q=Dustin+Cook+%22functionally+illiterate+fraud%22
    <https://findwhocallsyou.com/4234911448?CallerInfo>
    Dustin Cook: Functionally Illiterate Fraud
    Besides Peter the Klöwn, who doesn't know what I'm doing? Enjoy the housing in the overfull garbage dump of my KF. No-one gets it, I ain't done gone
    got it. That's what Peter the Klöwn does when he gets humiliated. He quickly creates a sock, starts a trolling thread so he can claim some lie. Hey it
    was my left hand... and then Peter the Klöwn talks to it with his right
    hand. Generally, I wouldn't call a claim like Peter the Klöwn's posts a fantasy right up until you negate it (as you are here) and Peter the Klöwn responds with the nothing but repetition without offering any evidence.
    Peter the Klöwn calls it "obsessing" over him, even though he continues
    to cause that exact standard.
    --
    Eight things to never feed your dog https://search.givewater.com/serp?q=Dustin+Cook+%22functionally+illiterate+fraud%22
    https://www.google.com/maps/place/108+Warrior+Dr,+Kingsport,+TN+37663/ https://www.google.com/search?q=Dustin%20Cook%20functionally%20illiterate%20fraud
    Dustin Cook: Functionally Illiterate Fraud
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Saturday, January 09, 2021 08:40:03
    From Newsgroup: comp.sys.mac.system

    On sam. 09 janvier 2021 (03:37),
    Király <me@home.spamsucks.ca> wrote:

    My tin 2.4.5 menu doesn't have that option, the last menu item is in
    positon 123.

    <https://imgur.com/4TqjqUs.png>

    You should start from scratch to have a current ~/.tin/tinrc

    From tin's source doc/INSTALL:

    #v+
    --with-editor=PROG (default: empty)
    Define if the standard editor should be anything other than the value of
    your EDITOR or VISUAL environment variable or, at as the last resort, vi.
    You can also add some default command line options to the editor. Users
    can overwrite this value by setting default_editor_format in their tinrc
    file.
    #v-

    Try using "default_editor_format" though "editor_format" just works here
    since more than 20yo.

    My head is spinning reading all of that. I'm just going to stick with my 10-year old version, tin 1.9.6. It uses the editor that I want and just works. I didn't find anything that 2.4.5 does better or even differently anyway.

    If 1.9.6 works and no changes[1] are useful for you, then yes no need to update ;)

    Many thanks for all the help everyone.

    You're welcome.

    [1] <ftp://ftp.tin.org/pub/news/clients/tin/stable/CHANGES>

    --
    Ourstor : Le club de musculation des geek vous propose sa definition du
    jour: developper couché = coder dans son lit
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From bje@bje@ripco.com to comp.sys.mac.system on Saturday, January 09, 2021 13:10:58
    From Newsgroup: comp.sys.mac.system

    Kir?ly <me@home.spamsucks.ca> wrote:

    : SHELL=/bin/zsh

    Well it's not working because you aren't using bash for a shell.

    I think the correct answer is .zshrc within your home directory.

    The format is the same of what to put in there as far as I know, but I
    don't use zsh.

    -bruce
    bje@ripco.com
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Saturday, January 09, 2021 17:02:09
    From Newsgroup: comp.sys.mac.system

    Matt <matt@lv426.eu.invalid> wrote:
    My tin 2.4.5 menu doesn't have that option, the last menu item is in positon 123.

    <https://imgur.com/4TqjqUs.png>

    Thank you, that was the clue I needed. Mine is on line 105. I just
    needed to put "nano" in front of that string of +%N %F, replacing %E. I
    now have tin 2.4.5 running with nano as the editor.

    Thanks for the help everyone. Hopefully I'll be good for at least a
    decade to come now.

    --
    K.

    Lang may yer lum reek.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Saturday, January 09, 2021 17:19:31
    From Newsgroup: comp.sys.mac.system

    On sam. 09 janvier 2021 (18:02),
    Király <me@home.spamsucks.ca> wrote:

    Thank you, that was the clue I needed. Mine is on line 105. I just
    needed to put "nano" in front of that string of +%N %F, replacing %E. I
    now have tin 2.4.5 running with nano as the editor.

    Yup, "%X" are just variables piped by tin to the external editor (%N for
    the line number, %F for the temprorary filename when you're editing a
    post, %E to use editor from shell's $EDITOR/$VISUAL, etc.)

    Thanks for the help everyone. Hopefully I'll be good for at least a
    decade to come now.

    And possibly more, using tin/tass since the 90s!

    --
    * fidou a quitté le chat (mettons les points sur les i, les barres sur les T et surtout les queues dans les Q)
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Saturday, January 09, 2021 19:45:04
    From Newsgroup: comp.sys.mac.system

    Matt <matt@lv426.eu.invalid> wrote:
    And possibly more, using tin/tass since the 90s!

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also
    had tin, and which all dropped command line access eventually. That's
    when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much,
    and still don't.

    --
    K.

    Lang may yer lum reek.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From goodmanp@goodmanp@comcast.net to comp.sys.mac.system on Saturday, January 09, 2021 15:12:05
    From Newsgroup: comp.sys.mac.system

    On Jan 9, 2021, Király wrote
    (in article <rtd140$gm0$1@dont-email.me>):

    Matt <matt@lv426.eu.invalid> wrote:
    And possibly more, using tin/tass since the 90s!

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also
    had tin, and which all dropped command line access eventually. That's
    when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much,
    and still don’t.

    My only experience with a command line newsreader was back when I was using Delphi as my ISP. Usenet access was through some type of virtual window that brought up NN as the newsreader. I am not sure how this all worked as this
    was not a shell account and I was accessing Delphi with a Windows dial up connection. Regardless, when I clicked on the link, NN was there and I didn’t have to compile or install anything. I liked using it a lot and
    spent a lot of time trying to figure out all of it’s features.I had a book written by Harley Hahn (I think that was who it was) that helped me with some of the basics. But the text editor was VI and I never was able to master that at all. I ended up typing my responses on a Windows text editor and pasting
    it into the article as a workaround. Delphi eventually dropped the service
    and when I switched to a Mac, I ended up using Unison and now Hogwasher. I like Hogwasher a lot and I am glad that it is still being developed. But
    there is a part of me that wished I had the knowledge to be able to set up and use a command line newsreader again...

    --
    Paul Goodman


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From STALKING_TARGET_08@frelwizzen@gmail.com to comp.sys.mac.system on Saturday, January 09, 2021 18:06:17
    From Newsgroup: comp.sys.mac.system

    On Saturday, January 9, 2021 at 12:45:08 PM UTC-7, Király wrote:
    Matt <ma...@lv426.eu.invalid> wrote:
    And possibly more, using tin/tass since the 90s!

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also
    had tin, and which all dropped command line access eventually. That's
    when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much,
    and still don't.
    --
    K.

    Lang may yer lum reek.
    Calls it "attacking" him, even though he continues to trigger that exact retort.
    You are nine seconds away from being in everyone's kill file.
    Gregory Hall claims to be the spreadsheet-teacher, let's see him put up
    a version but lacking the shipping/handling procedures.
    Reviewing macOS... still a rookie.
    Gregory Hall must understand that others can go get Access, right, medhead? Meanwhile, anyone can just ignore him, which renders *his* immature nonsense impotent, just like Gregory Hall.
    --
    Top 15 Ways Gregory Hall Trolls! https://search.givewater.com/serp?q=Dustin+Cook+%22functionally+illiterate+fraud%22
    https://www.bing.com/search?q=%22FUNCTIONALY%20ILLITERATE%20FRAUD%22
    Dustin Cook
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Fishrrman@Fishrrman2000@yahoo.com to comp.sys.mac.system on Saturday, January 09, 2021 23:13:41
    From Newsgroup: comp.sys.mac.system

    Will Unison work with the m1 Macs...?
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Your Name@YourName@YourISP.com to comp.sys.mac.system on Sunday, January 10, 2021 17:28:40
    From Newsgroup: comp.sys.mac.system

    On 2021-01-10 04:13:41 +0000, Fishrrman said:

    Will Unison work with the m1 Macs...?

    I don't have an M1 Mac, but Unison is 64bit, so it could work after
    Rosetta2 has translated it on the first run or if you reinstall it. It
    just depends on what system resources it taps into and whether or not
    they still exist - if it run in Big Sur on an Intel Mac, then it should
    run in Big Sur on an M1 Mac.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Lewis@g.kreme@kreme.dont-email.me to comp.sys.mac.system on Sunday, January 10, 2021 04:53:24
    From Newsgroup: comp.sys.mac.system

    In message <rtdutl$c3r$2@dont-email.me> Fishrrman <Fishrrman2000@yahoo.com> wrote:
    Will Unison work with the m1 Macs...?

    Does it run under Big Sur?

    --
    "Are you pondering what I'm pondering?"
    Pinky: I think so, Brain! (Sprays his breath)
    Brain: Er... then again, let's not let our enthusiasm
    overwhelm us!
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Your Name@YourName@YourISP.com to comp.sys.mac.system on Sunday, January 10, 2021 18:00:54
    From Newsgroup: comp.sys.mac.system

    On 2021-01-10 04:28:40 +0000, Your Name said:
    On 2021-01-10 04:13:41 +0000, Fishrrman said:

    Will Unison work with the m1 Macs...?

    I don't have an M1 Mac, but Unison is 64bit, so it could work after
    Rosetta2 has translated it on the first run or if you reinstall it. It
    just depends on what system resources it taps into and whether or not
    they still exist - if it runs in Big Sur on an Intel Mac, then it
    should run in Big Sur on an M1 Mac.

    Unison isn't listed on the "Is Apple silicon ready?" website yet <https://isapplesiliconready.com>

    You can request an app to be tested, but requests might be being done
    based on how many requests there are for it.

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From nospam@nospam@nospam.invalid to comp.sys.mac.system on Sunday, January 10, 2021 00:07:38
    From Newsgroup: comp.sys.mac.system

    In article <rte1m6$8os$1@gioia.aioe.org>, Your Name
    <YourName@YourISP.com> wrote:

    Unison isn't listed on the "Is Apple silicon ready?" website yet

    nor will it ever be since it's a dead product
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Sunday, January 10, 2021 08:54:53
    From Newsgroup: comp.sys.mac.system

    On sam. 09 janvier 2021 (20:45),
    Király <me@home.spamsucks.ca> wrote:

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also
    had tin, and which all dropped command line access eventually. That's
    when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much,
    and still don't.

    Almost the same scenario there. Used tass/tin through an rsh to my
    unisersity account and sticked to tin once I kept reading Usenet groups
    to this day after being graduate and moved to the "wild" life.

    God it does not make us younger :)

    --
    dahull: 2003 c'est comme xp
    bmx: non
    bmx: t'as pas un chien qui va chercher tes fichiers
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Matt@matt@lv426.eu.invalid to comp.sys.mac.system on Sunday, January 10, 2021 09:00:38
    From Newsgroup: comp.sys.mac.system

    On sam. 09 janvier 2021 (18:02),
    Király <me@home.spamsucks.ca> wrote:

    Thank you, that was the clue I needed. Mine is on line 105. I just
    needed to put "nano" in front of that string of +%N %F, replacing %E. I
    now have tin 2.4.5 running with nano as the editor.

    BTW, here's a nice tip to have colors in nano(1). Create a
    ~/.tin/tin.nanorc with the following content:

    #v+
    cat .tin/tin.nanorc
    ## Quoted usenet articles (under e.g. tin).
    ##
    syntax "tin"
    color red "^>.*"
    color blue "^>>.*"
    color green "^>>>.*"
    #v-

    And for ~/.nanorc :

    #v+
    cat .nanorc
    ## Quoted usenet articles (under e.g. tin)
    include "~/.tin/tin.nanorc"
    #v-

    --
    BUG : j'me fais cher sur internet
    BlackDeath : on sfait un CS?
    BlackDeath : Expression mondiale signifiant qu'on s'emmerde grave
    * bashfr.org
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Alan B@alanrichardbarker@nospamgmail.com.here to comp.sys.mac.system on Sunday, January 10, 2021 09:27:14
    From Newsgroup: comp.sys.mac.system

    On 2021-01-10, nospam <nospam@nospam.invalid> wrote:
    In article <rte1m6$8os$1@gioia.aioe.org>, Your Name
    <YourName@YourISP.com> wrote:

    Unison isn't listed on the "Is Apple silicon ready?" website yet

    nor will it ever be since it's a dead product

    It hasn't been actively developed for years. Out of interest, I tried it
    on Big Sur both on my Intel MBA and my M1 MBP with no joy on either. It
    didn't crash but its output was very corrupt.

    --
    Cheers, Alan
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Paul Goodman@goodmanp@comcast.net to comp.sys.mac.system on Sunday, January 10, 2021 13:23:41
    From Newsgroup: comp.sys.mac.system

    On Jan 10, 2021, Alan B wrote
    (in article<slrnrvli3i.gv.alanrichardbarker@alans-mbp.home>):

    On 2021-01-10, nospam<nospam@nospam.invalid> wrote:
    In article<rte1m6$8os$1@gioia.aioe.org>, Your Name
    <YourName@YourISP.com> wrote:

    Unison isn't listed on the "Is Apple silicon ready?" website yet

    nor will it ever be since it's a dead product

    It hasn't been actively developed for years. Out of interest, I tried it
    on Big Sur both on my Intel MBA and my M1 MBP with no joy on either. It didn't crash but its output was very corrupt.

    Same for me. I was using Unison up till the upgrade to Big Sur. After the upgrade, it would open up, but clicking on an article did nothing. It was at that point that I decided to try another program and switched to Hogwasher.

    --
    Paul Goodman


    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From me@me@home.spamsucks.ca (=?UTF-8?Q?Kir=C3=A1ly?=) to comp.sys.mac.system on Sunday, January 10, 2021 19:01:55
    From Newsgroup: comp.sys.mac.system

    Matt <matt@lv426.eu.invalid> wrote:
    Almost the same scenario there. Used tass/tin through an rsh to my unisersity account and sticked to tin once I kept reading Usenet groups
    to this day after being graduate and moved to the "wild" life.

    God it does not make us younger :)

    Yeah, at 46 I imagine I'm one of the younger people who frequents this newgroup. I have this idea that the majority here are over 70, I wonder
    how accurate that is.

    --
    K.

    Lang may yer lum reek.
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Elden@usenet.news@icloud.com to comp.sys.mac.system on Sunday, January 10, 2021 16:14:37
    From Newsgroup: comp.sys.mac.system

    On Jan 9, 2021, goodmanp@comcast.net wrote
    (in article<0001HW.25AA459500271BA570000F41F38F@news-central.giganews.com>):

    On Jan 9, 2021, Király wrote
    (in article <rtd140$gm0$1@dont-email.me>):

    Matt <matt@lv426.eu.invalid> wrote:
    And possibly more, using tin/tass since the 90s!

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also had tin, and which all dropped command line access eventually. That's
    when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much,
    and still don’t.

    My only experience with a command line newsreader was back when I was using Delphi as my ISP. Usenet access was through some type of virtual window that brought up NN as the newsreader. I am not sure how this all worked as this was not a shell account and I was accessing Delphi with a Windows dial up connection. Regardless, when I clicked on the link, NN was there and I didn’t have to compile or install anything. I liked using it a lot and spent a lot of time trying to figure out all of it’s features.I had a book written by Harley Hahn (I think that was who it was) that helped me with some of the basics. But the text editor was VI and I never was able to master that at all. I ended up typing my responses on a Windows text editor and pasting it into the article as a workaround. Delphi eventually dropped the service and when I switched to a Mac, I ended up using Unison and now Hogwasher. I like Hogwasher a lot and I am glad that it is still being developed. But there is a part of me that wished I had the knowledge to be able to set up and use a command line newsreader again...

    I also use Hogwasher and like it a lot. I spent a large amount of time
    working with the author/maintainer in patching a fair number of bugs a few years back. He may have seen me as a pain in the ass. But I see it as helping him to have a better product.

    However my favorite newsreader for many years was SLRN. Nothing like a nice plain text config that gives you such a huge amount of flexibility.


    -=Elden=-

    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From ant@ant@zimage.comANT (Ant) to comp.sys.mac.system on Sunday, January 10, 2021 23:14:14
    From Newsgroup: comp.sys.mac.system

    Kirly <me@home.spamsucks.ca> wrote:
    Matt <matt@lv426.eu.invalid> wrote:
    Almost the same scenario there. Used tass/tin through an rsh to my unisersity account and sticked to tin once I kept reading Usenet groups
    to this day after being graduate and moved to the "wild" life.

    God it does not make us younger :)

    Yeah, at 46 I imagine I'm one of the younger people who frequents this newgroup. I have this idea that the majority here are over 70, I wonder
    how accurate that is.

    Eh, I am younger than you. ;)
    --
    :) NY! Let's hope 2021 will be better, but it doesn't seem like it so far. :( Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
    /\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
    / /\ /\ \ Please nuke ANT if replying by e-mail.
    | |o o| |
    \ _ /
    ( )
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Alan B@alanrichardbarker@nospamgmail.com.here to comp.sys.mac.system on Monday, January 11, 2021 10:17:38
    From Newsgroup: comp.sys.mac.system

    On 2021-01-11, Elden <usenet.news@icloud.com> wrote:

    [snip]

    However my favorite newsreader for many years was SLRN. Nothing like a
    nice plain text config that gives you such a huge amount of
    flexibility.

    I've been using slrn part-time for a couple of years now and have to
    agree with you. I have not really explored all the configuration it
    offers yet. I've also been using Hogwasher and Usenapp plus Newstap on iOS/iPadOS.

    --
    Cheers, Alan
    --- Synchronet 3.18b-Win32 NewsLink 1.113
  • From Steve Carroll@frelwizzen@gmail.com to comp.sys.mac.system on Monday, January 11, 2021 06:12:02
    From Newsgroup: comp.sys.mac.system

    On Sunday, January 10, 2021 at 5:14:45 PM UTC-7, Elden wrote:
    On Jan 9, 2021, good...@comcast.net wrote
    (in article<0001HW.25AA459500...@news-central.giganews.com>):
    On Jan 9, 2021, Király wrote
    (in article <rtd140$gm0$1...@dont-email.me>):

    Matt <ma...@lv426.eu.invalid> wrote:
    And possibly more, using tin/tass since the 90s!

    Me too, since 1993. I was 19 then and accessed it by telnet into my university's server. Left university and went to private ISPs which also had tin, and which all dropped command line access eventually. That's when I had to install it on my own computer (original eMac) if I was to continue using it. I never liked any of the GUI usenet readers as much, and still don’t.

    My only experience with a command line newsreader was back when I was using
    Delphi as my ISP. Usenet access was through some type of virtual window that
    brought up NN as the newsreader. I am not sure how this all worked as this was not a shell account and I was accessing Delphi with a Windows dial up connection. Regardless, when I clicked on the link, NN was there and I didn’t have to compile or install anything. I liked using it a lot and spent a lot of time trying to figure out all of it’s features.I had a book
    written by Harley Hahn (I think that was who it was) that helped me with some
    of the basics. But the text editor was VI and I never was able to master that
    at all. I ended up typing my responses on a Windows text editor and pasting
    it into the article as a workaround. Delphi eventually dropped the service and when I switched to a Mac, I ended up using Unison and now Hogwasher. I like Hogwasher a lot and I am glad that it is still being developed. But there is a part of me that wished I had the knowledge to be able to set up and use a command line newsreader again...
    I also use Hogwasher and like it a lot. I spent a large amount of time working with the author/maintainer in patching a fair number of bugs a few years back. He may have seen me as a pain in the ass. But I see it as helping
    him to have a better product.

    However my favorite newsreader for many years was SLRN. Nothing like a nice plain text config that gives you such a huge amount of flexibility.


    -=Elden=-
    The Mack has a more advanced GUI. Which just pisses Peter 'The Fool'
    Köhlmann off.
    These posts are clearly *not* automated, they are made by a glue sniffing pervert with a personal vendetta who has way too much time on his hands.
    Try this - <https://www.google.com/search?q=dustin%20cook%20functionally%20illiterate%20fraud>
    And <https://duckduckgo.com/?q=dustin+cook+the+functionally+illiterate+fraud> No need even for the name Duston Cook: <https://www.bing.com/search?q=%22functionally%20illiterate%20fraud%22>
    A gross fabrication by Peter 'The Fool' Köhlmann. Theo did not deny
    authoring it, but he did not post it to usenet. Peter 'The Fool' Köhlmann
    did that, in an page that uses his work.... and he did it because he's obsessed with Peter 'The Fool' Köhlmann kicking his ass until you are crosseyed.
    Enough already. You're again trying to act like you know as much as
    Theo. You're the court jester and your many brainless programs show this.
    --
    "You'll notice how quickly he loses interest when everything is about
    him. He clearly wants the attention"
    Steven Petruzzellis, making the dumbest comment ever uttered.
    --- Synchronet 3.18b-Win32 NewsLink 1.113