From: Keith Thompson said:
if you have Emacs, then you have Gnus, the newsreader I use.
Does it have a feature of scanning *all* the newsgroups in the
whole world to find any followups to articles you have posted, so
that you can continue back-and-forth exchanges? Or do you first use
Google Groups to scan for followups, then somehow transfer the
message-ID from Google Groups to Gnus to do your actual followup?
What if the article has expired from your local NNTP server, so the
transfer from GG to NNTP doesn't work. What do you do then?
Do you use Gnus remotely over VT100 dialup?
How do you like editing with emacs through VT100 dialup compared to
having the text right there locally on your Macintosh where you can
use mouse to sweep text to copy&pages instead of the more laborous
way you have to do it with vt100-remote-emacs?
From 1975, when I got my first terminal (Beehive 3A) and modem, for
just a few years after that, my only from-home text editing was SOS
(Son Of Stopgap) via 300 baud acoustic coupler into Stanford A.I.
dialup. But then I discovered emacs at MIT-ML and later MIT-MC, and
with DM2500 emulator I wrote myself in 2k bytes of RAM on MOS-6502,
that was a great improvement over SOS. But then in 1990 I got my
own Macintosh, with various GUI text-editors which was a great
improvement over dialup/remote emacs. I still use emacs and vi for
special purposes, especially emacs for making tiny tweaks to lisp
code for live CGI applications, such as just last night and earlier
today I was improving my "all but one" flashcard program to fix two
problems, namely users who accidently back up to an earlier screen
and try to refresh (which totally confused the program as well as
the user, now it detects the problem and issues a clean ERROR
screen with link to reset to the top of the algorithm), and the
rare case where there is o card due yet and only one card coming up
due in the next five seconds but that card coming up is the same
card they had just-before done so it has to be skipped (until today
it'd sit for up to five seconds waiting for that card, and *then*
notice it couldn't be used because it was the just-previous card
and switch to whatever it would do if nothing were due, but now it
recognizes that special situation by a cleaner algorithm and
immediately goes on to whatever else it would do without the
wasteful up-to-5-second delay). But even those upgrades weren't
done entirely using remote emacs. At the start of the upgrade, I
copied fragments of useful code from the VT100 screen to a local
McSink edit, used local editing with mouse to compose my first
draft of the patch, used copy&pasge to transmit the patch back into
the remote-emacs edit buffer, and then used emacs parens-matching
to make sure I hadn't goofed the parens, then did the rest of the
edit with mostly emacs. It's quite rare that I do an entire edit
from begin to end using nothing but VT100-to-remote-emacs. It's
just too awkward when jumping all over a source file to collect
pieces of stuff and trying to assemble them together. Yeah, I can
use two-window mode with a scratch buffer in the other half, but
then the part of the code I can see at one time is so tiny as to be
painful in itself. So much more user/programmer friendly to have
access to two full-size windows, one remote-emacs and one
local-edit.
I don't know what you're using now.
Yeah, mySituation.html just tells the situation I have to deal with
here, not the coping strategies I use, such as how to browse
newsgroups and post to newsgroups and browse e-mail and send e-mail
etc. without any InterNet access at home. I wonder if I should
write a companion document that tells how I do such things? Until I
decide to write such a document, this below will have to suffice:
To browse newsgroups, I use mostly-broken Google Groups. There's no
longer (since 2.5 years ago) any way to browse threads in tree
view, only a very broken indented-outline view, and no way to jump
from outline view to the single article, making outline view
virtually useless. And since a few weeks ago there's no longer the
time-of-day in the search-result page, so when I click on an
article and get taken to first article in a group of 25 (instead of
the particular article I clicked on), it's a royal pain to find
which of those 25 is the article I wanted. So for the most part
it's hit-or-miss trying to find followups to what I previously
posted so that I can continue back-and-forth discussions. But at
least it's *possible* to find *some* of followups to what I posted,
so it's better than anything else that is availiable AFAIK.
To bookmark an article I want to respond to but don't have time
right away, or to actually compose my reply, I switch to "original"
version, which is **not** the original, it's *mostly* the original,
but with anything of the form alphanum@alphanum munged so I can't
see people's e-mail addresses. Also it has crap at top and bottom
of the Web page it shows. Still it does have the Message-ID field
and other key fields.
To bookmark an article, I copy the Message-ID from the "original"
page, and paste into a local McSink edit.
Later to fetch a bookmarked article, I go to Google Groups search
form where it has a place for look up message by ID, copy
Message-ID from McSink edit and past into GG form. Fortunately that
currently brings up just the one article, not group of 25, so it's
quick to skip two screens of garbage and click on "original" link.
Then to compose my reply, I copy the relevant header lines from the
GG "original" page and paste into McSink, manually rearrange them
so that References is immediately before Message-ID, delete the
Message-ID tag so it chains after the References, then check the
total size of that and trim the oldest parts as needed to reduce it
to 255 or fewer bytes (plus the newline making 256). Then I move
the From: line to be last of the header lines, and add two
characters "> " before it. Then I scroll lynx to bring up the body
of your message and copy various parts of it from lynx/GG screen
and paste into local McSink edit, paragraph-fill, and use
copy&paste to semi-manually insert "> " before each quoted line.
Then I compose my response.
When I'm ready to post, I copy&paste from the headers in that
message to the NNTP template just before it in the file. Then I
ctrl-Z out of lynx, ask Unix for the date&time, copy&paste the
time-of-day from Unix to McSink, but manually patch the date if
it's changed since I previously posted. Then I manually patch my
personal message-ID in the NNTP form. Then I copy&paste the TELNET
to NNTP server, wait for it to respond, type POST, wait for it to
respond, copy&paste the header from my template, wait for it to
finish uploading, copy&paste the message-body, wait for it to
finish uploading, manually type period on line by itself, wait for
it to respond that posting was successful, manually type QUIT
command, wait for it to quit telnet, then CUT the message body from
McSink and paste into a different McSink edit which is
already-posted but not-yet-verified.
Unless you're typing NNTP protocol commands directly,
Well, I think you now know I'm in the "unless" case here, OK?
I haven't a clue what your problem with attribution lines is, ...
It's not my problem. It's your problem.
There's nothing wrong with my methods. It's your nitpicking which is wrong.