Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: info-gnus-english@gnu.org
Subject: Re: Automatically authenticating at local imap server
Date: Tue, 05 Feb 2008 13:16:46 +0100	[thread overview]
Message-ID: <87hcgnk381.fsf@member.fsf.org> (raw)
In-Reply-To: <kztzknhdy3.fsf@kafka.physik3.gwdg.de>

David <de_bb@arcor.de> writes:

Hi David,

>> ,----[ C-h f gnus-summary-refer-article RET ]
>> | gnus-summary-refer-article is an interactive compiled Lisp function in `gnus-sum.el'.
>> | (gnus-summary-refer-article message-id)
>> | 
>> | Fetch an article specified by message-id.
>> `----
>
> Ah, OK. I only tried nnimap-retrieve-headers with a message-id and it
> didn't work.

BTW, I have tested this with my rather large (10000+ messages)
emacs-devel group, and it's quite fast.  I enter the summary buffer with
`C-u 0 RET' so that no articles are displayed and then do `M-x
gnus-summary-refer-article RET <message-id>'.  Even with m-ids of
ancient articles I don't get a noticable delay.  Maybe dovecot does some
indexing to make that possible.  At least the feature list says:

  Dovecot's indexes are self-optimizing. They contain exactly what the
  user's client commonly needs, no more and no less.

Seems the message-id is included there.

Bye,
Tassilo
-- 
Chuck  Norris  doesn't  daydream.  He's  too busy  giving  other  people
nightmares.

  reply	other threads:[~2008-02-05 12:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6898.1202031751.18990.info-gnus-english@gnu.org>
2008-02-03 20:29 ` Gour
2008-02-04  8:39   ` Tassilo Horn
2008-02-04 14:33     ` David
2008-02-04 19:40       ` Tassilo Horn
2008-02-04 22:22         ` David
2008-02-05  8:32           ` Tassilo Horn
2008-02-05 10:53             ` David
2008-02-05 12:16               ` Tassilo Horn [this message]
     [not found]         ` <mailman.6972.1202163783.18990.info-gnus-english@gnu.org>
2008-02-05 17:00           ` Ted Zlatanov
2008-02-05 21:58             ` David
2008-02-06  9:17               ` Tassilo Horn
2008-02-06 11:56                 ` David
2008-02-06 23:03                   ` new version of nnmairix.el (was: Automatically authenticating at local imap server) David
     [not found]             ` <mailman.7011.1202248745.18990.info-gnus-english@gnu.org>
2008-02-06 15:24               ` Automatically authenticating at local imap server Ted Zlatanov
2008-02-06 20:07                 ` David
     [not found]                 ` <mailman.7050.1202328476.18990.info-gnus-english@gnu.org>
2008-02-15 22:35                   ` Ted Zlatanov
2008-02-23 17:55                     ` Registry not registering duplicate articles (was: Automatically authenticating at local imap server) David
     [not found]                     ` <mailman.7831.1203789258.18990.info-gnus-english@gnu.org>
2008-02-26 16:54                       ` Registry not registering duplicate articles Ted Zlatanov
2008-02-26 18:20                         ` Ted Zlatanov
2008-02-03  9:42 Automatically authenticating at local imap server Tassilo Horn
2008-02-03 11:00 ` Reiner Steib
2008-02-04  9:06   ` Tassilo Horn
2008-02-06 20:17     ` Reiner Steib
2008-02-07  9:57       ` Tassilo Horn

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=87hcgnk381.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --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).