Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Can I do this with the registry?
Date: Fri, 20 Mar 2009 14:27:20 -0500	[thread overview]
Message-ID: <86k56kngfb.fsf@lifelogs.com> (raw)
In-Reply-To: <m2bps3wd07.fsf@zreba.luannocracy.com>

On Sat, 14 Mar 2009 22:50:32 -0700 David Abrahams <dave@boostpro.com> wrote: 

DA> For various reasons, I need to delete messages from my INBOX when I'm
DA> done with them.  Often someone will send me a reply and fail to quote
DA> important context, or I'll simply need to go back and review earlier
DA> messages in the thread.  I keep a "history" folder that essentially
DA> accumulates everything that's passed through my email flow, so I have
DA> the messages, but to find them I have to do lots of navigation.  Oh, and
DA> sometimes I don't "have" all the messages, but they're available on some
DA> NNTP group I subscribe to, because threads get "taken offline" (or the
DA> opposite).

DA> I'd really like a way to collect all the messages connected to a thread,
DA> no matter which groups the thread has passed through.  Can the registry
DA> help with that, and if so, how?

The registry can give you the following for a message ID: sender,
subject, mtime, and groups for that message.  You can also associate
persistent flags with a message.

What you need can be done by looking at the group for each message ID
you need, looking for the message itself, and putting it in a list.
Then you can get the References for the parent message and recurse.  

I think you're asking for the list of messages to be interpreted as a
virtual thread inside the current group, which is pretty hard and I
don't know how to do it.  Displaying the message contents in some way,
though, is not too hard.

Ted




  reply	other threads:[~2009-03-20 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15  5:50 David Abrahams
2009-03-20 19:27 ` Ted Zlatanov [this message]
2009-03-20 20:07   ` David Abrahams
2009-03-20 21:26     ` 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=86k56kngfb.fsf@lifelogs.com \
    --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).