Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Generate buffer containing only undownloaded
Date: Wed, 26 Nov 2003 08:00:03 -0600	[thread overview]
Message-ID: <ubrqzs00s.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <m3u14ri9sm.fsf@newsguy.com>

Harry Putnam <reader@newsguy.com> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
> [...]
>
>>> I find that I often have a few undownloaded messages mixed in with
>>> many downloaded ones.  Due to my reading habits no doubt.  Even
>>> though the category predicate is `true'.  I rarely go unplugged so
>>> sometimes read messages before they are downloaded which I think is
>>> what causes the random undownloaded messages.
>>
>> I may have a solution for this one.  Add
>> gnus-agent-fetch-selected-article to the gnus-select-article-hook.
>> This will result in undownloaded messages being downloaded to the
>> agent as you read them.
>
> Oh, this looks promising... yes.  ... Thanks
>
>>> Anyway, how can I sort a few dozen undownloaded into a display from a
>>> summary of buffer of several thousand?
>>
>> How about an alternative solution?
>>
>> Use 'M-^ 1 0 0 0 0 J #' to mark all articles for fetching then use
>> 'J S' to fetch them.  The nice part is that the agent will only fetch
>> those articles that have not already been fetched.
>
> That is what I've been doing, but its a bit labor intensive.  Takes a
> fair bit of time.  But worse is the fact that all readedness marks
> leave town with that solution. ... (on whatever gets downloaded)
> Not a very good solution but yes, it does work.

Set gnus-agent-mark-unread-after-downloaded to nil.

Kevin



  reply	other threads:[~2003-11-26 14:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  4:27 Harry Putnam
2003-11-26  6:30 ` Kevin Greiner
2003-11-26 12:39   ` Harry Putnam
2003-11-26 14:00     ` Kevin Greiner [this message]
2003-11-26 15:19       ` Harry Putnam

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=ubrqzs00s.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).