Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David <de_bb@arcor.de>
To: info-gnus-english@gnu.org
Subject: Re: Automatically authenticating at local imap server
Date: Tue, 05 Feb 2008 22:58:49 +0100	[thread overview]
Message-ID: <874pcncbfq.fsf@arcor.de> (raw)
In-Reply-To: <861w7ruyme.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:
> D> Jumping to the original message in this group is another problem
> D> since we only know the message-id but not the article
> D> number. 
>
> You could use the Gnus registry if it's loaded.  It will tell you the
> last place a message ID was seen (it learns this by looking at the
> visible messages every time you enter a group, and by hooking into
> spool/move/copy/delete on each backend).  

Yes, I guess the best way would be to first check the registry for the
group and do the additional mairix search only if the registry is not
loaded or does not know the location of the message. I don't want to
rely solely on the registry though, because of the limitations you
describe:

> It may not know the location for various reasons, e.g. the user limits
> the size of the registry or the message hasn't been seen yet, 

I guess the latter would be a problem for users with big archive groups
which they rarely open.

> The registry doesn't currently record the article number, but it could.

The article number won't be necessary as Tassilo already mentioned. The
lookup through gnus-read-header works just fine.

-David

  reply	other threads:[~2008-02-05 21:58 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
     [not found]         ` <mailman.6972.1202163783.18990.info-gnus-english@gnu.org>
2008-02-05 17:00           ` Ted Zlatanov
2008-02-05 21:58             ` David [this message]
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=874pcncbfq.fsf@arcor.de \
    --to=de_bb@arcor.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).