From: Reiner Steib <reinersteib+gmane@imap.cc>
To: info-gnus-english@gnu.org
Subject: Re: Why is gnus-summary-insert-new-articles considered a limiting command?
Date: Sat, 20 Oct 2007 23:10:19 +0200 [thread overview]
Message-ID: <v9odeta3wk.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <6gqpu4-5ig.ln1@karme.afraid.org>
On Sat, Oct 20 2007, Jens Thiele wrote:
> On 11 Okt 2007, Ferran.Jorba@uab.cat wrote:
>> a while ago I learned that the fast (right? optimal?) way to update my
>> imap inbox is with gnus-summary-insert-new-articles (bound to `/ N').
>> However, I've noticed that gnus-summary-pop-limit (`/ w') reverts the
>> situation. This is strange, moreover when I do some *real* limiting
>> (by subject or author) and then, when I pop those limits Gnus happily
>> goes back to the situation when I first updated my inbox with `/ N',
>> maybe a few hours ago.
So it's how a limiting command is supposed to behave, isn't it?
>> Perhaps I'm not using the right command to update my inbox? Which
>> should I use?
>
> I use gnus-summary-rescan-group (bound to "M-g" in the summary buffer)
`/ N' is supposed to be faster than `M-g'.
>> Or, why is gnus-summary-insert-new-articles considered a limiting
>> (instead of an updating) command, other than they appear in the
>> same page [1] of the manual?
I don't know why it was implemented like this. Does anyone recall?
Maybe you can find something in the archives. It has been added in
2001:
,----[ ChangeLog.2 ]
| 2001-02-22 22:00:00 ShengHuo ZHU <zsh@cs.rochester.edu>
|
| * gnus-sum.el (gnus-fetch-headers): New function.
| (gnus-select-newsgroup): Use it.
| (gnus-summary-insert-articles): New function.
| (gnus-summary-insert-old-articles): New function.
| (gnus-summary-insert-new-articles): New function.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-10-20 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 7:51 Ferran Jorba
2007-10-20 17:29 ` Jens Thiele
2007-10-20 21:10 ` Reiner Steib [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=v9odeta3wk.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=info-gnus-english@gnu.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).