From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: marking articles when reading them
Date: 01 Nov 2000 00:35:24 +0100 [thread overview]
Message-ID: <vafem0wzirn.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <q6md7ggrdqg.fsf@spartacus.utdallas.edu>
On 31 Oct 2000, amos+lists.ding@utdallas.edu wrote:
>
> What I'd like to see, to go along with `(display . all)', is
> something like `gnus-no-more-than-x-messages'. This might be set to
> a small value, like a couple of hundred or so, for faster folder
> access. Then if I wanted more of the messages, I could just do `C-u
> M-g', and it would prompt me for how many messages to include.
Does (setq gnus-fetch-old-headers 423) do the job?
> Actually, I still use PINE or something to dig around in folders if
> I want to find something particular. One difficulty I have with
> gnus/nnimap is that if I have *all* my folders listed in my
> .newsrc.eld, starting up gnus hits the mail server rather hard as it
> goes and digs through that long folder list of mine. So I try to
> keep gnus only knowledgeable about the folders that I frequently
> access, which means I use another IMAP client to quickly query
> something.
You can kill some groups, then Gnus won't query the server about
them. But you have to use `j' in the group buffer to jump to them, or
`A k' to get a list of all killed groups.
But there is a potential problem with nnimap. When you start Gnus,
does it say `checking mailbox foo' or does it say `updating info for
foo'? The former is dramatically faster than the latter.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~2000-10-31 23:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 15:12 Kai Großjohann
2000-07-07 15:37 ` David S. Goldberg
2000-07-07 16:57 ` Kai Großjohann
2000-10-31 19:51 ` Amos Gouaux
2000-10-31 23:35 ` Kai Großjohann [this message]
2000-11-01 20:20 ` Amos Gouaux
2000-11-02 10:18 ` Kai Großjohann
2000-11-09 3:47 ` Amos Gouaux
2000-07-07 16:03 ` François Pinard
2000-10-31 19:27 ` Amos Gouaux
2000-10-31 23:32 ` Kai Großjohann
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=vafem0wzirn.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).