From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Agent fetch : only for specific agentised group?
Date: Wed, 30 Mar 2011 16:17:04 +0200 [thread overview]
Message-ID: <oi4o6ky9pb.fsf@news.eternal-september.org> (raw)
In-Reply-To: <pkn8vvwir2z.fsf@this.is.really.invalid> (Robert Pluim's message of "Wed, 30 Mar 2011 17:08:20 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>>
>>> Richard Riley <rileyrg@googlemail.com> writes:
>>>
>>>> I can M-g on a group to only fetch headers for that group when
>>>> plugged. But how to limit the agent to only downloading articles for
>>>> that group when I do Js? As it is its going for all (agent) groups and
>>>> doesn't appear to be limited by any level prefix/config. Again,
>>>> potentially expensive when roaming. Something I am missing or misusing?
>>>
>>> What's wrong with J-u (which respects the prefix mark as well, so you can
>>> mark groups with '#' first).?
>>>
>>> Robert
>>
>> Nothing wrong with it at all. Thanks - totally missed it. missed that
>> J-u in the manual and it doesnt appear in C-h m for the group buffer.
>>
>
> I tend to use C-h b to find bindings. I think the J- bindings are not
> part of the group-mode, but of the group-agent mode, so they don't
> appear in the C-h m display.
I'll try that some more. I cant think why I didnt spot that in the
manual. I spent about 2 hours re-reading the level and group stuff last
night too. I was so wrapped up in groups/levels/subscribed/activate
levels/plugged/agent etc I probably couldnt see the wood for the trees;)
My task for after dinner tonight is to try and figure out why I am still
confused about foreign groups and servers as there seems to be a big
discrepancy between how it works and how its documented. e.g drafts
being a foreign group.
prev parent reply other threads:[~2011-03-30 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 13:48 Richard Riley
2011-03-30 14:52 ` Robert Pluim
2011-03-30 14:04 ` Richard Riley
2011-03-30 15:08 ` Robert Pluim
2011-03-30 14:17 ` Richard Riley [this message]
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=oi4o6ky9pb.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).