From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Subject: Re: nnir.el error
Date: Tue, 13 Jun 2006 00:12:33 +0200 [thread overview]
Message-ID: <871wtut44u.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <873beasubv.fsf@nokile.rath.org> (Nikolaus Rath's message of "Mon, 12 Jun 2006 09:32:04 +0200")
Nikolaus Rath <Nikolaus@rath.org> writes:
> Whatever. Using the new file the error is now indeed different, but
> still not very helpful:
>
> Debugger entered--Lisp error: (error "Unknown header type nil while requesting article 1265 of group nnml:home.nikratio.Gnus.Groups.Archiv.2000")
Well, at least the (bogus) group name and the backend queried are in
there now. But I concur that the error reporting could be better.
Perhaps we could use gnus-request-group to figure out if the group
actually exists, as nnvirtual does[1]. But I guess I'll wait with
further changes so Sascha's outstanding patches apply cleanly.
Thanks for testing,
andreas
[1] While it calls gnus-request-group, it doesn't really check for an
error, but I guess the chances for it to run into a nonexisting
group are negligible.
next prev parent reply other threads:[~2006-06-12 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 13:45 Nikolaus Rath
2006-06-08 5:47 ` Andreas Seltenreich
2006-06-08 9:49 ` Nikolaus Rath
2006-06-09 18:59 ` Andreas Seltenreich
2006-06-10 3:41 ` Andreas Seltenreich
2006-06-10 20:49 ` Nikolaus Rath
2006-06-10 22:07 ` Andreas Seltenreich
2006-06-11 10:43 ` Nikolaus Rath
2006-06-11 11:35 ` Reiner Steib
2006-06-11 12:14 ` Nikolaus Rath
2006-06-11 21:07 ` Reiner Steib
2006-06-11 14:51 ` Andreas Seltenreich
2006-06-12 7:32 ` Nikolaus Rath
2006-06-12 22:12 ` Andreas Seltenreich [this message]
2006-06-10 7:06 ` Nikolaus Rath
2006-06-10 7:59 ` Andreas Seltenreich
2006-06-10 9:30 ` Nikolaus Rath
2006-06-08 9:56 ` Nikolaus Rath
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=871wtut44u.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.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).