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 12:56:23 +0100	[thread overview]
Message-ID: <kzhcgmwb6g.fsf@musil.physik3.gwdg.de> (raw)
In-Reply-To: <871w7qtpea.fsf@member.fsf.org>

Tassilo Horn <tassilo@member.fsf.org> writes:
> One annoying thing is that it seems I must use (gnus-group-select-group
> 1), if I provide 0 or nil, the group won't be selected.  So you'll have
> another message in the group after you press "M-^" in the nnmairix
> group.

Yes, but you can limit the summary buffer to the message containing the
message-id. I'd suggest the following:

(defun th-gnus-registry-select-article (message-id)
  (interactive "sMessage-ID: ")
  (let ((group-buffer (get-buffer gnus-group-buffer))
        (group (gnus-registry-fetch-group message-id)))
    (pop-to-buffer group-buffer)
    (gnus-group-jump-to-group group)
    (gnus-summary-read-group group 1 t nil nil nil nil)	
    (gnus-summary-refer-article message-id)
    (gnus-summary-limit-to-headers (format "message-id: %s" message-id))
    (gnus-summary-select-article)))

I'm currently working on the code that finds the original group based on
the message file path. As soon as this is ready I'll post an update to
nnmairix also containing the registry code.

Thanks for your input,
David

  reply	other threads:[~2008-02-06 11:56 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 [this message]
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=kzhcgmwb6g.fsf@musil.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).