From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: nnir, gnus-goto-article and such
Date: Tue, 27 Sep 2011 12:04:56 -0400 [thread overview]
Message-ID: <m2aa9q0y53.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87pqinvvg4.fsf@lifelogs.com>
on Mon Sep 26 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
DA> on Wed Sep 21 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
>>> Then the registry should be able to tell you what group it came from,
>>> too, I think?
>
> DA> Maybe... I'm still not sure how to use it. But I'll take another look.
>
> Simply call it like this (for message-ID "34"):
>
> (gnus-registry-get-id-key "34" 'group)
> (gnus-registry-get-id-key "34" 'subject)
So here's an example where I tried it out.
(defun gnus-goto-article (message-id)
(with-temp-buffer
(erase-buffer)
;; Insert dummy article
(insert (format "From nobody Tue Sep 13 22:05:34 2011\n\n"))
(gnus-group-read-ephemeral-group message-id
`(nndoc ,message-id
(nndoc-address ,(current-buffer))
(nndoc-article-type mbox))
'activate
(not 'quit-config)
(not 'request-only)
'(-1) ; 'select-articles
(not 'parameters)
0 ; ' number
)
(gnus-summary-refer-article message-id)
(message "group from registry: %s" (gnus-registry-get-id-key message-id 'group))
))
I queried the registry at the point where I'd like to know the group of
that article. Unfortunately, I get back nil. And if I wanted to
conjure up an article number, well, it's -1, so that's not going to be
much help, is it?
It seems like this shouldn't be so hard...
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
prev parent reply other threads:[~2011-09-27 16:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:24 Dave Abrahams
2011-09-16 15:05 ` gnus-warp-to-article (was: nnir, gnus-goto-article and such) Dave Abrahams
2011-09-21 18:03 ` nnir, gnus-goto-article and such Lars Magne Ingebrigtsen
2011-09-21 21:16 ` John Wiegley
2011-09-22 13:01 ` Andrew Cohen
2011-09-26 19:17 ` Lars Magne Ingebrigtsen
2011-09-26 20:46 ` Dave Abrahams
2011-09-27 7:04 ` John Wiegley
2011-09-27 15:36 ` Dave Abrahams
2011-09-26 20:01 ` Dave Abrahams
2011-09-26 21:35 ` Ted Zlatanov
2011-09-27 15:35 ` Dave Abrahams
2011-09-27 21:12 ` Ted Zlatanov
2011-09-28 14:34 ` Dave Abrahams
2011-09-29 0:32 ` Ted Zlatanov
2011-09-29 1:19 ` Dave Abrahams
2011-09-29 2:06 ` Dave Abrahams
2011-09-29 8:27 ` Ted Zlatanov
2011-09-29 13:40 ` Dave Abrahams
2011-09-29 14:00 ` Ted Zlatanov
2011-09-29 14:40 ` Dave Abrahams
2011-09-29 14:58 ` Ted Zlatanov
2011-09-29 20:04 ` Dave Abrahams
2011-09-29 23:40 ` Ted Zlatanov
2011-09-29 8:22 ` Ted Zlatanov
2011-09-27 16:04 ` Dave Abrahams [this message]
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=m2aa9q0y53.fsf@pluto.luannocracy.com \
--to=dave@boostpro.com \
--cc=ding@gnus.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).