From: Lynbech Christian <christian.lynbech@tieto.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "ding@gnus.org" <ding@gnus.org>
Subject: Re: cleaning out old nnml groups
Date: Mon, 4 Feb 2019 16:58:28 +0100 [thread overview]
Message-ID: <ytqpo97r1r6j.fsf@tieto.com> (raw)
In-Reply-To: <868sz39zss.fsf@zoho.eu> (Emanuel Berg's message of "Tue, 29 Jan 2019 17:46:59 +0100")
Thanks, that will work nicely.
RE RFC3676: I know, I know, I will fix it.
-- Christian
-----------------------
On Tue, Jan 29 2019, Emanuel Berg wrote:
Lynbech Christian wrote:
> Over the years of uisng gnus, I have
> accumulated a number of nnml groups that can
> be seen when going into the server but where
> the corresponding directory no longer exists.
>
> They are still known to gnus since (I assume)
> they are still present in the active file.
>
> Is there a simple and/or safe way to clean up
> the active file, other than to edit it
> directly? It does not appear that the command
> gnus-group-check-bogus-groups does anything
> to nnml groups.
`gnus-group-delete-group'?
> ------------------------+-----------------------------------------------------
> Christian Lynbech | christian #\@ defun #\. dk
> ------------------------+-----------------------------------------------------
> Hit the philistines three times over the head
> with the Elisp reference manual.
> -
> petonic@hal.com (Michael A. Petonic)
Hint: RFC 3676, section 4.3 (Usenet Signature Convention)
https://www.ietf.org/rfc/rfc3676.txt
--
underground experts united
http://user.it.uu.se/~embe8573
prev parent reply other threads:[~2019-02-04 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 8:20 Lynbech Christian
2019-01-29 16:46 ` Emanuel Berg
2019-02-04 15:58 ` Lynbech Christian [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=ytqpo97r1r6j.fsf@tieto.com \
--to=christian.lynbech@tieto.com \
--cc=ding@gnus.org \
--cc=moasenwood@zoho.eu \
/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).