From: Jesper Harder <harder@myrealbox.com>
Subject: Re: bogus nnml groups
Date: Sat, 28 Sep 2002 03:55:44 +0200 [thread overview]
Message-ID: <m3n0q27u8v.fsf@defun.localdomain> (raw)
In-Reply-To: <m3hegbwg6j.fsf@mordack.codesourcery.com>
Ricardo Anguiano <anguiano@codesourcery.com> writes:
> Jesper Harder <harder@myrealbox.com> writes:
>
>> What do you get, when you evaluate this expression:
>>
>> (gnus-active "GROUP")
>
> (gnus-active "expire.freebsd.qa")
> (83 . 85)
Hmm, that's strange. The condition Gnus uses for determining if a group
is bogus is:
(unless (or (gnus-active group) ; Active
(gnus-info-method info)) ; Foreign
;; Found a bogus newsgroup.
(push group bogus))
So, if (gnus-active group) returns a non-nil value -- as it does in your
case -- the group isn't considered bogus. I don't understand how it
could happen anyway.
As a workaround you could set `gnus-expert-user' to nil. Then I think
you'll at least be asked for confimation before a bogus group is
removed.
prev parent reply other threads:[~2002-09-28 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 22:02 Ricardo Anguiano
2002-09-27 1:59 ` Jesper Harder
[not found] ` <m3hegbwg6j.fsf@mordack.codesourcery.com>
2002-09-28 1:55 ` Jesper Harder [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=m3n0q27u8v.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).