From: egallego@babel.ls.fi.upm.es (Emilio Jesús Gallego Arias)
To: ding@gnus.org
Subject: Re: catchup all groups
Date: Thu, 08 Jul 2010 01:29:23 +0200 [thread overview]
Message-ID: <87hbkalvl8.fsf@babel.ls.fi.upm.es> (raw)
In-Reply-To: <87vd8r58nw.fsf@topper.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> On Wed, 07 Jul 2010 16:32:16 -0400, Sean wrote:
>
>> After I've poked through all of the groups that I'm subscribed to, is
>> there an alternative in the group buffer to `c,y,c,y,c,y, ...'?
>
> Mark the groups you want to catch up using '#' (process mark) and then
> catch up with 'c'?
>
> (You can mark the next, say, 10 groups with 'C-u 10 #')
Or use Topics and have a top level topic. Then pressing `c' in the topic
line will mark as read every child group.
next prev parent reply other threads:[~2010-07-07 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 20:32 Sean Sieger
2010-07-07 20:38 ` Adam Sjøgren
2010-07-07 23:29 ` Emilio Jesús Gallego Arias [this message]
2010-07-07 23:33 ` Sean Sieger
2010-07-08 6:34 ` Reiner Steib
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=87hbkalvl8.fsf@babel.ls.fi.upm.es \
--to=egallego@babel.ls.fi.upm.es \
--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).