From: Jochem Huhmann <joh@gmx.net>
Subject: Re: 423 bad article number from local spool but header are there?
Date: Mon, 02 Dec 2002 19:59:11 +0100 [thread overview]
Message-ID: <874r9wtfgg.fsf@nova.revier.com> (raw)
In-Reply-To: <v9isyccmoe.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4uce.02.r.steib@gmx.net> writes:
> JFTR: Oort Gnus v0.07 (see Jochem's header) doesn't have Kevin's agent
> code (dunno if this is relevant or not).
Well, I don't know too.
>> I've never used Agent intentionally and I'm also not on the Gnus
>> mailing list
>
> When using Oort, it's recommended to read ding. The change concerning
> the agent was announced in the news file (GNUS-NEWS).
Yep, but I'm still just a Gnus user and have more than enough other
lists to follow. I tried Oort for the new pgp/gpg-support and kept it
since I had no problems with it.
>> (Gnus does not have a gnus-report-bug).
>
> What's wrong with `M-x gnus-bug RET'? ;-)
Err... Nothing, I just looked for a function similar to report-bug ;-)
Good to know, thanks.
Anyway, I don't have a problem reporting something that looks clearly
like a bug. But this behaviour being just a little bit unexpected with
ticked articles and the agent is something quite not so clear. I even
don't know how the agent is supposed to work since I've never needed nor
used it. I will still just file a bug report stating what I know if
nobody more current with Oort and more knowledgeable about agent will
take care.
Jochem
next prev parent reply other threads:[~2002-12-02 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3d6ooxxx7.fsf@ccs.covici.com>
2002-11-30 3:05 ` Jesper Harder
2002-11-30 12:13 ` John Covici
[not found] ` <873cpjw7lh.fsf@nova.revier.com>
[not found] ` <84u1hzasf9.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <878yz9uxdg.fsf@nova.revier.com>
2002-12-02 7:53 ` Kai Großjohann
2002-12-02 17:33 ` Jochem Huhmann
[not found] ` <v9isyccmoe.fsf@marauder.physik.uni-ulm.de>
2002-12-02 18:59 ` Jochem Huhmann [this message]
2002-12-02 20:12 ` Kai Großjohann
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=874r9wtfgg.fsf@nova.revier.com \
--to=joh@gmx.net \
/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).