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: Wed, 06 Feb 2008 21:07:31 +0100	[thread overview]
Message-ID: <87prv9n918.fsf@physik3.gwdg.de> (raw)
In-Reply-To: <86ve52nm4d.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:
> D> Yes, I guess the best way would be to first check the registry for the
> D> group and do the additional mairix search only if the registry is not
> D> loaded or does not know the location of the message. I don't want to
> D> rely solely on the registry though, because of the limitations you
> D> describe: [...]
>
> Cool.  Also note the group could be wrong, e.g. someone modified a
> Maildir spool externally and the registry doesn't know.  So it's a bit
> like asking a random person for directions: very nice when it works but
> don't rely on it :)

When the user notices that the registry is wrong he will be able revert
to the file path method by calling the function with a prefix.

I also noticed that when the same message is in two different groups the
registry will only return the group where it first saw it, right? I
guess it would be quite difficult to extend the registry in a way so
that it can return all groups where a message exists?

-David

  reply	other threads:[~2008-02-06 20:07 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
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 [this message]
     [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=87prv9n918.fsf@physik3.gwdg.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).