From: Tassilo Horn <tassilo@member.fsf.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, ding@gnus.org
Subject: Re: Bug with referring articles
Date: Wed, 15 Jun 2011 20:29:43 +0200 [thread overview]
Message-ID: <87boxzhrs8.fsf@member.fsf.org> (raw)
In-Reply-To: <m2vcw7av3k.wl%dave@boostpro.com> (Dave Abrahams's message of "Wed, 15 Jun 2011 12:59:59 -0400")
Dave Abrahams <dave@boostpro.com> writes:
Hi Dave,
> Well, I did some hacking around and some edebugging based on what you
> pointed me at, and I was able to use some advice to get
> `nnimap-find-article-by-message-id' to always look in my archive
> group, and it found the article, but then of course the rest of
> nnimap-request-article failed.
>
> I wonder if it would be reasonably easy to hack up a "derived" select
> method based on nnimap that always forces itself to use one particular
> group (mailbox)?
That matches your usecase, but it's not very general...
Out of couriosity, I just process-marked all ~12 folders of one of my
imap servers in *Group* and did
C-u G G HEADER Message-ID <87d3ig2qcf.fsf@yun.yagibdah.de> RET imap RET
to search for lee's moved message in all folders containing about 50.000
messages in total using a plain IMAP seach. The nnir result buffer
contained this single message and the search over all groups took about
3 seconds. So basically, I think it would be reasonable try nnir imap
searches in the `current' refer method if that is imap. And of course,
that should be shortcutting. In my search, actually the first group
(INBOX) contained the message I was looking for, so there was no reason
to search the other groups as well.
Bye,
Tassilo
--
Sent from my Emacs
next prev parent reply other threads:[~2011-06-15 18:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 18:43 chasing mail threads Dave Abrahams
2011-06-14 20:57 ` Andreas Schwab
2011-06-15 4:30 ` Dave Abrahams
2011-06-15 7:42 ` Bug with referring articles (was: chasing mail threads) Tassilo Horn
2011-06-15 8:01 ` Dave Abrahams
2011-06-15 16:59 ` Dave Abrahams
2011-06-15 18:29 ` Tassilo Horn [this message]
2011-06-15 22:16 ` Bug with referring articles Dave Abrahams
2011-06-15 22:20 ` Dave Abrahams
2011-06-16 6:01 ` Vegard Vesterheim
2011-06-16 11:45 ` Andrew Cohen
2011-06-16 18:08 ` Dave Abrahams
2011-06-16 6:51 ` Tassilo Horn
2011-06-16 18:10 ` Dave Abrahams
2011-06-16 19:51 ` Tassilo Horn
2011-06-17 1:06 ` Ted Zlatanov
2011-06-17 7:30 ` Tassilo Horn
2011-06-28 14:23 ` Ted Zlatanov
2011-06-28 18:01 ` Tassilo Horn
2011-06-28 18:50 ` Ted Zlatanov
2011-06-17 11:30 ` Andrew Cohen
2011-06-30 22:54 ` Dave Abrahams
2011-06-30 23:02 ` Lars Magne Ingebrigtsen
2011-06-30 23:02 ` Andrew Cohen
2011-07-01 22:15 ` Tassilo Horn
2011-07-01 22:39 ` Andrew Cohen
2011-07-01 22:50 ` Tassilo Horn
2011-07-01 23:48 ` Andrew Cohen
2011-07-02 10:33 ` Tassilo Horn
2011-07-02 12:02 ` Andrew Cohen
2011-07-02 15:23 ` Tassilo Horn
2011-07-02 12:43 ` Andrew Cohen
2011-07-02 15:11 ` Tassilo Horn
2011-07-11 19:12 ` Dave Abrahams
2011-06-21 13:21 ` Andrew Cohen
2011-06-22 6:38 ` Tassilo Horn
2011-06-26 9:40 ` Lars Magne Ingebrigtsen
2011-06-27 17:48 ` Andrew Cohen
2011-06-27 17:55 ` Tassilo Horn
2011-06-30 2:24 ` Lars Magne Ingebrigtsen
2011-06-30 17:07 ` Andrew Cohen
2011-07-11 19:34 ` Dave Abrahams
2011-07-13 12:15 ` Andrew Cohen
2011-07-13 19:09 ` Dave Abrahams
2011-07-13 21:40 ` Andrew Cohen
2011-07-11 18:44 ` Dave Abrahams
2011-06-14 23:59 ` chasing mail threads prad
2011-06-15 9:57 ` Steinar Bang
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=87boxzhrs8.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=schwab@linux-m68k.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).