Gnus development mailing list
 help / color / mirror / Atom feed
From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: C y on really large groups
Date: Tue, 10 May 2011 18:16:37 +0200	[thread overview]
Message-ID: <87zkmulee2.fsf@gmail.com> (raw)
In-Reply-To: <87zkmumtny.fsf@member.fsf.org>

10/05/11 18:01, Tassilo Horn
> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>> I just tried subscribing to a random group on gmane with more than
>> 50000 articles in it and did C y on it in the *Group* buffer. It was
>> instant; it took a fraction of a second.
>
> I don't have a C-prefix keymap at all?!?  In *Group*, `C' is bound to:
>
> ,----[ C-h k C RET ]
> | C runs the command gnus-group-catchup-current-all, which is an interactive
> | compiled Lisp function in `gnus-group.el'.
> | 
> | It is bound to C, <menu-bar> <Group> <Catch up all articles>.
> | 
> | (gnus-group-catchup-current-all &optional N)
> | 
> | Mark all articles in current newsgroup as read.
> | Cross references (Xref: header) of articles are ignored.
> `----
>
> But that's according to the docs:
>
> ,----[ (info "(gnus)Group Data") ]
> | `C'
> |      Mark all articles in this group, even the ticked ones, as read
> |      (`gnus-group-catchup-current-all').
> `----
>
> What am I missing?

He's just doing "y" to confirm ;-)

FWIW, it's instant here as well.




  parent reply	other threads:[~2011-05-10 16:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 14:44 Didier Verna
2011-05-10 15:40 ` Adam Sjøgren
2011-05-10 16:01   ` Tassilo Horn
2011-05-10 16:09     ` Adam Sjøgren
2011-05-10 19:57       ` Tassilo Horn
2011-05-10 16:16     ` Antoine Levitt [this message]
2011-05-11  7:53       ` Didier Verna
2011-05-11  8:15         ` Didier Verna
2011-05-11  8:19           ` Didier Verna
2011-05-11  8:56             ` Didier Verna
2011-05-11 21:47               ` Ted Zlatanov
2011-05-30 20:06                 ` 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=87zkmulee2.fsf@gmail.com \
    --to=antoine.levitt@gmail.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).