From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: Quassia, Agent mode, what happens if you forget Js after a g when plugged?
Date: 27 Feb 1998 09:46:20 -0800 [thread overview]
Message-ID: <sdu39l3pqr.fsf@oakdale.ucdavis.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Feb 1998 13:19:02 +0100"
>>>>> On 27 Feb 1998 13:19:02 +0100, Lars Magne Ingebrigtsen <larsi@gnus.org> said:
>> When plugged, what happen if you do a g and forget to make a Js?
>> will the new article be retrive on the next Js (following another
>> g?)
LMI> Yes.
Although, Lars, I've noticed another problem with the agent where the
summary buffers get confused when you do a 'g J s', time passes, 'g J
j', enter group.
I think the new articles fetched by the last g are not shown (if I
remember correctly) at all. I guess gnus doesn't have the headers, so
this makes some sense. However, I think that when you do a catch up
(in the summary buffer, not the group buffer) it marks the new ones
(not shown) as read as well, which is wrong. I'm pulling most of this
from memory as I noticed it last month or something like that and
never submitted a bug report. Anyway, the entry to the problem is the
same if the actual problem description is not quite correct.
LMI> If they were marked with "@", that means that Gnus had decided to
LMI> just download the headers, and not the articles themselves. If
LMI> you are dissatisfied with Gnus' decision, you should tell Gnus by
LMI> modifying the category download predicate.
And hence my suggestion to at least mark them as % on an attempted
read command with a following (message "... marked for download").
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-02-27 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-27 10:08 Francois Felix Ingrand
1998-02-27 12:19 ` Lars Magne Ingebrigtsen
1998-02-27 16:03 ` Francois Felix Ingrand
1998-02-28 5:49 ` Lars Magne Ingebrigtsen
1998-03-02 9:40 ` Francois Felix Ingrand
1998-03-07 12:55 ` Lars Magne Ingebrigtsen
1998-02-27 17:46 ` Wes Hardaker [this message]
1998-02-28 5:51 ` Lars Magne Ingebrigtsen
1998-03-02 16:35 ` Wes Hardaker
1998-03-07 12:55 ` Lars Magne Ingebrigtsen
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=sdu39l3pqr.fsf@oakdale.ucdavis.edu \
--to=wjhardaker@ucdavis.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).