From: Dave Abrahams <dave@boostpro.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>, ding@gnus.org
Subject: Re: Bug with referring articles
Date: Thu, 16 Jun 2011 14:10:02 -0400 [thread overview]
Message-ID: <m2zklhzlz9.wl%dave@boostpro.com> (raw)
In-Reply-To: <87oc1y1d6i.fsf@member.fsf.org>
At Thu, 16 Jun 2011 08:51:49 +0200,
Tassilo Horn wrote:
>
> Firstly, the current code for referring articles is broken, because
> only the first method in `gnus-refer-article-method' is actually
> tried as I've explained in <87fwnbr15c.fsf@fastmail.fm>. So that
> has to be fixed anyway.
>
> Secondly, I think that the `current' method may perform nnir searches
> over all groups of that server if the article cannot be found in the
> current group and nnir is configured properly, as it is by default for
> IMAP. Or alternatively, there might be some new `current-nnir' method.
>
> However, I have to admit that this is only some conceptual talk. I have
> no real clue how the code is supposed to work, and this whole summary
> updating doesn't look too trivial. :-)
Is there a place where we can put this information so that it will be
treated as a bug report, and someone who has the missing clue might
respond?
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-06-16 18:10 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 ` Bug with referring articles Tassilo Horn
2011-06-15 22:16 ` 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 [this message]
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=m2zklhzlz9.wl%dave@boostpro.com \
--to=dave@boostpro.com \
--cc=ding@gnus.org \
--cc=schwab@linux-m68k.org \
--cc=tassilo@member.fsf.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).