From: jbw@cs.bu.edu (Joe Wells)
Subject: Re: miscellaneous Gnus problems/questions
Date: Thu, 13 Jun 1996 22:10:36 -0400 [thread overview]
Message-ID: <199606140210.WAA08408@csb.bu.edu> (raw)
In-Reply-To: Jason L Tibbitts III's message of 12 Jun 1996 01:03:39 -0500
In article <ufa4tohpnic.fsf@sina.hpc.uh.edu> Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
JW> 6. The help text for "I a ?" lists match types that are not legal in
JW> combination with "a". It also has a duplicate description for match
JW> type "r".
Still does. Most likely a left-out feature (have to write bunches of help
texts to fix it).
Just write one piece of help text for each letter and then insert the help
texts in the help buffer only for the letters that apply.
JW> 18. I have noticed when reading the group
JW> nndir+/ftp@ftp.hpc.uh.edu:/pub/emacs/ding-list-recent/:ding.recent
That's me.
JW> that some of the read marks often get lost when I revisit the
JW> group. I can't figure out why this is happening.
Odd. Nobody else has reported it anywhere I've seen. I don't renumber the
articles, just delete the old ones, so I can't say. Anyone else seen this
one? If upgrading doesn't cure it, let me know.
I seem to notice this happening when I switch from home to my office. I
never exit from Emacs; I leave it running for months. At home, I use an
Emacs running under iScreen. At my office, I use an Emacs connected to my
X display. When I leave my office (or home), I quit Gnus ("q" in *Group*
buffer). Then I restart Gnus (M-x gnus) when I get home (or to my
office).
--
Joe Wells <jbw@cs.bu.edu>
next prev parent reply other threads:[~1996-06-14 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-12 4:11 Joe Wells
1996-06-12 6:03 ` Jason L Tibbitts III
1996-06-12 21:25 ` Ken Olstad
1996-06-14 2:10 ` Joe Wells [this message]
1996-06-14 4:56 ` Jason L Tibbitts III
1996-06-12 7:42 ` Per Abrahamsen
1996-06-12 7:51 ` Joe Wells
1996-06-12 8:17 ` Per Abrahamsen
1996-06-14 15:30 ` Kai Grossjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199606140210.WAA08408@csb.bu.edu \
--to=jbw@cs.bu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).