From: Ansgar Burchardt <ansgar@2007.43-1.org>
To: ding@gnus.org
Subject: Re: cannot always fetch parent article
Date: Thu, 09 Aug 2007 15:18:01 +0200 [thread overview]
Message-ID: <gnus-86y7gk3kza.fsf@wg42.homeip.net> (raw)
In-Reply-To: <b4mzm12tjt9.fsf@jpl.org>
Katsumi Yamaoka wrote:
>>>>>> Ansgar Burchardt wrote:
>> If I post a followup to an article to a different group (e.g. a random
>> *.test group) and then try to fetch the parent article it works without
>> problems. The problem only occurs if the parent was posted in the
>> same group as the followup and Gnus tries to guess the article number.
>> If Gnus behaved as in the first case, everything would be fine.
>
> I studied how Gnus refers to parent articles, and realized that
> Gnus uses an article number only when a parent article is in the
> current group. Could you try the patch attached below?
[ patch introducing nntp-xref-number-is-evil snipped ]
The patch solves the problem. Thank you.
Ansgar
next prev parent reply other threads:[~2007-08-09 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 14:47 Ansgar Burchardt
2007-08-07 3:18 ` Katsumi Yamaoka
2007-08-07 16:49 ` Ansgar Burchardt
2007-08-08 10:14 ` Katsumi Yamaoka
2007-08-09 13:18 ` Ansgar Burchardt [this message]
2007-08-10 2:34 ` Katsumi Yamaoka
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=gnus-86y7gk3kza.fsf@wg42.homeip.net \
--to=ansgar@2007.43-1.org \
--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).