Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Getting message details from message-sent-hook
Date: Thu, 29 May 2003 13:30:23 -0400	[thread overview]
Message-ID: <4nznl5slsg.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87r86h3i5q.fsf@kruhft.vc.shawcable.net> (Burton Samograd's message of "29 May 2003 08:08:01 -0700")

On 29 May 2003, kruhft@hotmail.com wrote:
> Bill White <billw@wolfram.com> writes:
> 
>> Now, can some function grab the message id and jump to that
>> article?  Perhaps using Ted's registry stuff?
> 
> I was thinking that there would be something available to select a
> message-id but I haven't gotten around to looking for it.  It just
> seemed like a good thing to have in there because I'm sure someone
> will write that functionality someday (maybe even me if I get
> inspired :)

The registry can help:

gnus-registry-fetch-group is a compiled Lisp function in `gnus-registry'.
(gnus-registry-fetch-group ID)

Get the group of a message, based on the message ID.
Returns the first place where the trail finds a group name.

Three issues:

- the group name is currently not prefixed, so you don't know the
  server.  I'll work on that, but time has been short lately.

- the registry may be inaccurate, e.g. someone deletes a IMAP message
  outside this instance of Gnus

- there may be more than one copy of the message (and thus, multiple
  groups in the registry trail)

If anyone is interested in using the registry as a generic message-ID
locator, patches or ideas are welcome.

Ted



  reply	other threads:[~2003-05-29 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 17:51 Burton Samograd
2003-05-28 19:25 ` Burton Samograd
2003-05-29  3:22   ` Bill White
2003-05-29 15:08     ` Burton Samograd
2003-05-29 17:30       ` Ted Zlatanov [this message]
2003-05-28 19:57 ` Johan Bockgård
2003-05-28 20:14 ` Benjamin Rutt

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=4nznl5slsg.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.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).