From: Gernot Hassenpflug <gh@nospam.com>
Subject: Re: how to remove groups entirely from .newsrc.eld file?
Date: Wed, 08 Jun 2005 22:19:18 +0900 [thread overview]
Message-ID: <877jh5yoix.fsf@nospam.com> (raw)
In-Reply-To: <m2psuxtd9b.fsf@seki.fr>
>>>>> "Sébastien" == Sébastien Kirche <sebastien.kirche.no@spam.free.fr.invalid> writes:
Sébastien> Le 8 Jun 2005 à 06:06, Gernot Hassenpflug s'est exprimé
Sébastien> ainsi :
>> Do I have to edit the .newsrc.eld file by hand to get rid of
>> it?
Sébastien> While recently playing with archives groups and
Sébastien> creating several bogus servers i found that sometimes
Sébastien> the only way to get rid of a server definition is to
Sébastien> manually edit .newsrc.eld files (when Gnus is not
Sébastien> started) and to edit the gnus-server-alist definition.
Sébastien> As else in the server buffer Gnus keeps on refusing to
Sébastien> kill some of them.
Hello Sébastien, many thanks for your helpful reply. I did edit the
.newsrc.eld file for the gnus-server-alist definition. Solved the
problem.
>> On a related note, anything done with G D appears in the
>> .newsrc.eld file, as expected,...
Sébastien> I think that .gnus.el should be considered more as an
Sébastien> initialisation script that actually a config file.
Sébastien> (Except for the customize section in the .emacs file
Sébastien> that one can place elsewhere) Gnus does not modify its
Sébastien> starting script but stores its configuration in the
Sébastien> .newsrc.eld file.
OK, now that that is clarified, I feel much better. I remember the
days of .newsrc files that were simple multi-column lists of newsgroup
names and article numbers. Things have gotten more complex!
>> Is there a recommended method for keeping mail safely organized
>> (easy to overview in the .gnus.el file, for example, not so
>> easy if you don't know where on disk(s) your groups were
>> located if you have to try and look for them again), and can I
>> move stuff that is created with G D into my .gnus.el file?
Sébastien> Maybe you can do like me for some settings : looking in
Sébastien> the .newsrc.eld for the parameters that gnus set and
Sébastien> copying them to the .gnus to keep them in case of
Sébastien> future reuse. I used to see that those settings are
Sébastien> ignored from the .gnus if they are also present in the
Sébastien> .newsrc.eld (so you have to remove them from
Sébastien> .newsrc.eld before they are taken into account if you
Sébastien> modify the .gnus definition).
OK, that sounds good to me. I'll give that a try. I've gained new
respect for the .newsrc.eld file, and back it up regularly too, in
case of accidental clearing.
Many thanks,
Gernot
--
G Hassenpflug RASC, Kyoto University
next prev parent reply other threads:[~2005-06-08 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 4:45 Gernot Hassenpflug
2005-06-08 9:21 ` Sébastien Kirche
2005-06-08 13:19 ` Gernot Hassenpflug [this message]
2005-06-08 14:49 ` Sébastien Kirche
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=877jh5yoix.fsf@nospam.com \
--to=gh@nospam.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).