From: David Moore <dmoore@UCSD.EDU>
Subject: Re: time delay on news groups?
Date: 13 Dec 1996 00:33:07 -0800 [thread overview]
Message-ID: <rvenguzvwc.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 13 Dec 1996 08:37:37 +0100
Wesley.Hardaker@sphys.unil.ch writes:
> Well, you can't put it in gnus-summary-prepare-hook or you'll get an
> infinite loop, I'm afraid... However, my next question is what does
> gnus do when you limit the buffer and then do a catchup? IE, do the
> limited articles get caught up as well?
I thought it only caught up the ones in the limited selection.
_However_, it marks all of the other hidden articles as read. And I do
mean read, if catchup would normally mark them as expirable, they just
get marked as read.
That's rather a pain, maybe catch up should be fixed not to do
that. Although I'm sure someone will say it's a feature. ;)
--
David Moore <dmoore@ucsd.edu> | Computer Systems Lab __o
UCSD Dept. Computer Science - 0114 | Work: (619) 534-8604 _ \<,_
La Jolla, CA 92093-0114 | Fax: (619) 534-1445 (_)/ (_)
<URL:http://oj.egbt.org/dmoore/> | In a cloud bones of steel.
next prev parent reply other threads:[~1996-12-13 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-12 20:53 Mark Eichin
1996-12-12 22:00 ` David Moore
1996-12-13 7:37 ` Wesley.Hardaker
1996-12-13 8:33 ` David Moore [this message]
1996-12-16 13:04 ` Lars Magne Ingebrigtsen
1996-12-12 22:37 St. Suika Fenderson Roberts
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=rvenguzvwc.fsf@sdnp5.ucsd.edu \
--to=dmoore@ucsd.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).