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 (was: chasing mail threads)
Date: Wed, 15 Jun 2011 04:01:22 -0400 [thread overview]
Message-ID: <m21uyvcylp.wl%dave@boostpro.com> (raw)
In-Reply-To: <87fwnbr15c.fsf@fastmail.fm>
Tassilo,
Thanks very much for your thorough reply; if we can solve this problem
it will make it possible for me to switch back to Gnus, which I would
dearly like to do.
At Wed, 15 Jun 2011 09:42:39 +0200,
Tassilo Horn wrote:
>
> Dave Abrahams <dave@boostpro.com> writes:
>
> Hi Dave,
>
> >> See gnus-refer-article-method.
> >
> > Okay, I see it. I do appreciate the hint, but it's practically
> > undocumented, and I'm not familiar enough with Gnus internals to have
> > any idea how to take advantage of it. Could you perhaps elaborate a
> > bit?
>
> ,----[ C-h v gnus-refer-article-method RET ]
> | gnus-refer-article-method is a variable defined in `gnus.el'.
> | Its value is (current
> | (nnregistry)
> | (nnweb "gmane"
> | (nnweb-type gmane))
> | (nnweb "google"
> | (nnweb-type google)))
> |
> | Original value was current
> `----
>
> So my setting for referring articles means,
>
> - try to find the message in the current select method,
> - if that doesn't work, query the registry,
> - if that doesn't work, ask gmane via the web,
> - if all fails, try google groups.
Ah, very nice!
> The second entry requires the gnus registry, of course. So you have to
> initialize it in your ~/.gnus.el with
>
> (gnus-registry-initialize)
Sure.
> I'm not completely sure, but I have the gut feeling that `current'
> should actually work for IMAP (you are using IMAP, right?).
Yes, I am.
> But that's the default value, and you say it doesn't work for you...
Well, it never has in the past. I can try again...
Nope, it doesn't work. `A T' doesn't do anything interesting, and `^'
now inserts a pseudo-article (which is a new behavior since last time
I tried this, which was a while ago).
<snip good analysis>
> The problem is that `gnus-summary-insert-subject' doesn't find the
> referred article (1), although its on the same server but a different
> IMAP folder. But instead it inserts a pseudo-article and returns 0,
> thus the `when' succeeds and 'found is thrown and no other refer methods
> are tried.
>
> IMHO, the pseudo-article should be inserted only after all refer methods
> failed...
>
> (1) Is it correct that IMAP has no way to find a message by Message-ID
> in all folders?
I think maybe that is correct. In my case, I'm even willing to tell
it what folder to search in, but it looks like Gnus doesn't give me a
way to express that. I tried using the nnimap-inbox option, but that
didn't seem to lead anywhere.
Thanks again
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2011-06-15 8:01 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 [this message]
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
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=m21uyvcylp.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).