From: Sacha Chua <sacha@free.net.ph>
Subject: Canonical way to find messages by message-id
Date: Sun, 15 Aug 2004 23:04:35 +0800 [thread overview]
Message-ID: <87vffkcuik.fsf@sacha.ateneo.edu> (raw)
Hello, everyone!
What is the canonical way to find a message by message ID? I maintain
planner.el, and right now we're doing it with this code snippet:
(defun planner-gnus-browse-url (url)
"If this is a Gnus URL, jump to it."
(when (string-match "^gnus://\\(.+\\)/\\(.+\\)" url)
(let ((group (match-string 1 url))
(article (match-string 2 url)))
(gnus-fetch-group group 1)
(or (gnus-summary-goto-article article nil t)
(when (fboundp 'gnus-summary-insert-cached-articles)
(gnus-summary-insert-cached-articles)
(gnus-summary-goto-article article nil t))
(message "Message could not be found."))
t)))
where an example URL would be
gnus://mail.planner/<20040813162910.GA3241@khazad-dum>
Unfortunately, (gnus-fetch-group group 1) fails when the most recent
message is no longer in the group, and we occasionally have problems
with cached articles.
(gnus-fetch-group group) sorta works if we remember to specify a large
enough number of messages, but the prompt can be slightly annoying.
Loading all messages and waiting for the summary to display takes a
lot of time.
Is there a way to quickly jump to a specific message given the message
ID, and then display the article and the summary buffer with just that
message in it? I tried tracing through some functions in the summary
and article code, but got pretty lost. <sheepish grin>
Thanks for your help!
--
Sacha Chua <sacha@free.net.ph> - open source geekette
interests: emacs, gnu/linux, making computer science education fun
wearable computing, personal information management
http://sacha.free.net.ph/ - PGP Key ID: 0xE7FDF77C
next reply other threads:[~2004-08-15 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 15:04 Sacha Chua [this message]
2004-08-16 17:38 ` Ted Zlatanov
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=87vffkcuik.fsf@sacha.ateneo.edu \
--to=sacha@free.net.ph \
/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).