From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: agent/fetch only articles from certain levels
Date: Fri, 25 Mar 2011 11:53:52 +0100 [thread overview]
Message-ID: <3waagj1nen.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87zkokei6u.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 24 Mar 2011 13:55:53 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Is there a way to make the default key binding for
>> gnus-group-get-new-news only fetch from a certain configured level and
>> below? I dont see it from the docstring. I do see I can prefix each time
>> but using agent and data roaming , the common use case would be for
>> "rescan" to only rescan high priority (or low level..) groups where the
>> boundary is a configured level (if set to nil it rescans all).
>>
>
> I have gnus-activate-level set to 2 for this reason with most groups'
> levels set at 3 except for the high priority ones. 'g' is the command
> for rescanning (getting email into/from) groups.
>
> Assuming I understood your question correctly, of course ;-)
Yes thats kind of it. Now let me explain (my!) confusion.
The behaviour *unplugged* is where I'm at. Since unplugged you are using
the agent then it makes little sense to me not to activate subscribed
groups. I have already done a C-u 5 g in plugged mode to scan all level
5 and below followed by a Js to download. If I then quit gnus and
restart later (gnus-unplugged is my new "on holiday" default start) then
since I can *see* the subscribed groups (the level of subscridness means
they are subscribed and visible) then there is no immediately obvious
reason not to activate them in unplugged too since its just a case of
displaying the group line activated with the already stored unread
count. As it is I need to C-u 5 g again (unplugged). Does this make some
kind of sense?
next prev parent reply other threads:[~2011-03-25 10:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 12:18 Richard Riley
2011-03-24 13:55 ` Eric S Fraga
2011-03-25 10:53 ` Richard Riley [this message]
2011-03-25 12:03 ` Eric S Fraga
2011-03-25 15:04 ` Richard Riley
2011-03-25 15:23 ` Richard Riley
2011-03-25 18:34 ` Richard Riley
2011-03-25 15:58 ` Eric S Fraga
2011-03-25 19:21 ` Adam Sjøgren
2011-03-25 21:05 ` Eric S Fraga
2011-03-25 21:13 ` Adam Sjøgren
2011-03-26 7:45 ` Richard Riley
2011-03-26 12:47 ` Adam Sjøgren
2011-03-27 7:15 ` Richard Riley
2011-03-27 7:25 ` Richard Riley
2011-03-27 17:38 ` Eric S Fraga
2011-03-28 15:03 ` Richard Riley
2011-03-28 17:07 ` Eric S Fraga
2011-03-28 16:33 ` Richard Riley
2011-03-28 18:13 ` Eric S Fraga
2011-03-29 7:26 ` Richard Riley
2011-03-29 17:06 ` Eric S Fraga
2011-03-26 7:43 ` Richard Riley
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=3waagj1nen.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
/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).