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.
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>
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>
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.The two current M1 supported Usenet clients which are well supported are:
Thanks.
Usenapp
<https://www.usenapp.com>
...and Hogwasher
<https://www.asar.com/hogwasher.html>
--
Regards,
Savageduck
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?
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, 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.
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.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.
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.
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.
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.
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?
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>
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.
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. :-(
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.
macOS 12 won't be around for probably around 10 years or more
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 moreDoubtful. 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)
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.
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.
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.
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.
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?
Formulaeaustin libpointing the_platinum_searcher tinysvm
Casksabricotine eclipse-testing prowritingaid syncsettings tinymediamanager
Yep, they're in ~/.tin. Just need to get a compiled tin binary. http://tin.org has its source
code. Maybe brew has it?
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.
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
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$ brew search tin
code. Maybe brew has it?
Formulaeaustin 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
Casksabricotine 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).
--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
My biggest problem is that Steve insists on serving PURPLE Kool Aid,
an I don't like PURPLE <sip sip> Kool Aid.
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 sourceI copied my ~/.tin folder from my old Mac to my new one. It wasn't as easy as that.
code. Maybe brew has it?
% ./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.
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.
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?
It's tin 1.9.6, released in November of 2010
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
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.
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.
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.
USENET is meant to be plain text, so that shouldn't include accented characters anyway.
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.
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.
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.
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.
Then change it either within tin's menu or directly on your ~/.tin/tinrc
For using nano (check nano's path on your system).
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.
nospam <nos...@nospam.invalid> wrote:It's like a prank call. Kelly Phillips has already decided what he is going
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.
...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?
Kir?ly <m...@home.spamsucks.ca> wrote:
...but it didn't do anything. tin is still using vi to compose.Tin mostly relies on environmental variables.
Google and the tin man page aren't helping me. Any other ideas?
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
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
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
You can check your work with .bash_profile by this (in terminal):
env
The NNTPSERVER, EDITOR and VISUAL should be listed there.
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.
b...@ripco.com wrote:The most obvious answer: Snit's Bitch David Brooks's consumed recreational drugs since then, and 'disremembered'.
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/picoThanks, I tried that, but bash seems to have ignored it; tin is still
export VISUAL=/usr/bin/pico
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?
On Friday, January 8, 2021 at 10:01:19 AM UTC-7, b...@ripco.com wrote: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
Kir?ly <m...@home.spamsucks.ca> wrote:
...but it didn't do anything. tin is still using vi to compose.Tin mostly relies on environmental variables.
Google and the tin man page aren't helping me. Any other ideas?
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.
-bruceWas that meant to be to Jeff Relf?
b...@ripco.com
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
My tin 2.4.5 menu doesn't have that option, the last menu item is in
positon 123.
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.
: SHELL=/bin/zsh
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.
And possibly more, using tin/tass since the 90s!
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.
Matt <ma...@lv426.eu.invalid> wrote:Calls it "attacking" him, even though he continues to trigger that exact retort.
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.
Will Unison work with the m1 Macs...?
Will Unison work with the m1 Macs...?
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
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.
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.
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
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.
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 :)
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...
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.
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.
On Jan 9, 2021, good...@comcast.net wroteThe Mack has a more advanced GUI. Which just pisses Peter 'The Fool'
(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 usingI 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
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...
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=-
Sysop: | Gate Keeper |
---|---|
Location: | Shelby, NC |
Users: | 790 |
Nodes: | 20 (0 / 20) |
Uptime: | 42:20:27 |
Calls: | 12,115 |
Files: | 5,294 |
D/L today: |
1 files (0K bytes) |
Messages: | 564,964 |