From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnregistry problem
Date: Mon, 28 Feb 2011 12:45:58 -0600 [thread overview]
Message-ID: <87ipw40zh5.fsf@lifelogs.com> (raw)
In-Reply-To: <87ei6se23k.fsf@gnu.org>
On Mon, 28 Feb 2011 14:10:55 +0100 ludo@gnu.org (Ludovic Courtès) wrote:
LC> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Thu, 24 Feb 2011 11:58:03 +0100 ludo@gnu.org (Ludovic Courtès) wrote:
>>
>>>> I was reading gmane.emacs.gnus.general and read the message
>>>> from Norbet Koch with the subject "Re: Your public key".
>>>>
>>>> Message-ID: <ygf8vxonnj7.fsf@vserv.viteno.net>
>>>>
>>>> I typed ^ (gnus-summary-refer-parent-article) and got the
>>>> message:
>>>>
>>>> No such function: nnregistry-request-group
>>>>
>>>> I now saw in the *Summary* buffer:
>>>>
>>>> n/a│O │nobody ║ ● (none)
>>
LC> I get the same situation, which indicates that nnregistry couldn’t find
LC> the article in the registry; *Messages* shows this:
>>
LC> nnregistry: requesting article `fake+none+gmane.emacs.gnus.general+-2' in group `nil'
LC> Fetched article <87y65ouqa5.fsf@keller.adm.naquadah.org>
LC> No such article (may have expired or been canceled)
>>
LC> I agree that this is suboptimal but I’m not sure what to do.
>>
>> The fake article shouldn't be displayed?
LC> There should be a message indicating that the article couldn’t be found
LC> but the summary should be left as is, I think (like when hitting ^ on a
LC> message with no references.)
Can you do this or should I (or Lars) get to it?
Thanks
Ted
prev parent reply other threads:[~2011-02-28 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 2:27 nyc4bos
2011-02-13 19:31 ` Lars Ingebrigtsen
2011-02-20 5:48 ` nyc4bos
2011-02-20 7:57 ` Lars Ingebrigtsen
2011-02-24 10:55 ` Ludovic Courtès
2011-02-25 3:34 ` Lars Ingebrigtsen
2011-02-24 10:58 ` Ludovic Courtès
2011-02-24 16:31 ` Ted Zlatanov
2011-02-28 13:10 ` Ludovic Courtès
2011-02-28 18:45 ` Ted Zlatanov [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=87ipw40zh5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).