Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Cc: John Wiegley <johnw@boostpro.com>
Subject: nnir and agent (was: `gnus-refer-article-methods' and `gnus-summary-refer-thread')
Date: Fri, 29 Jul 2011 13:05:10 -0400	[thread overview]
Message-ID: <m2fwlpt3uh.fsf_-_@pluto.luannocracy.com> (raw)
In-Reply-To: <m2oc0kdhqt.fsf@pluto.luannocracy.com>


on Sat Jul 23 2011, Dave Abrahams <dave-AT-boostpro.com> wrote:

> on Sat Jul 23 2011, Andrew Cohen <cohen-AT-andy.bu.edu> wrote:
>
>>>>>>> "Dave" == Dave Abrahams <dave@boostpro.com> writes:
>>
>>     Dave> on Sat Jul 23 2011, Andrew Cohen <cohen-AT-andy.bu.edu> wrote:
>>     >>>>>>> "Dave" == Dave Abrahams <dave@boostpro.com> writes:
>>     >> 
>>     Dave> Well, as mentioned earlier, I'm only interested in looking in
>>     Dave> *one* other group on the server.  But I'd also like to find
>>     Dave> messages in the registry and agent if possible (hey, why not
>>     Dave> ask for the moon, I figure?).
>>
>> I wouldn't think the registry or the agent have any info that isn't also
>> obtained from the search? 
>
> Well, no, but they can be accessed offline ;-)

I notice that the agent *does* have an effect on nnir: I was unable to
find a thread with `G G <message-id>' until after I had done `M-x
gnus-agent-expire-group RET RET' on the group.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com




      reply	other threads:[~2011-07-29 17:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 20:13 `gnus-refer-article-methods' and `gnus-summary-refer-thread' Dave Abrahams
2011-07-23  0:20 ` Andrew Cohen
2011-07-23 15:28   ` Dave Abrahams
2011-07-23 16:02     ` Andrew Cohen
2011-07-23 17:16       ` Dave Abrahams
2011-07-23 17:25         ` Andrew Cohen
2011-07-23 17:33           ` Dave Abrahams
2011-07-29 17:05             ` 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=m2fwlpt3uh.fsf_-_@pluto.luannocracy.com \
    --to=dave@boostpro.com \
    --cc=ding@gnus.org \
    --cc=johnw@boostpro.com \
    /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).