From: Harry Putnam <reader@newsguy.com>
Subject: Losing G p (group params)
Date: 26 Feb 2001 08:27:53 -0800 [thread overview]
Message-ID: <m3y9ut5s07.fsf@gnus.cvs.983032537> (raw)
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
[ Message posted to gnu.emacs.gnus and ding list ]
It has happened to me on several occasions where I inadvertantly
either kill a group or groups and there by loose the group param
settings.
I do keep backups of .newsrc.eld but often don't notice the problem
until quite a lot of new material has been written to .newsrc.eld,
making bodily overwrite with backup a non starter. Meaning only the
tedious hand route will restore things.
Especially painful if you have to resort to `G c' (group customize) to
remind you how some things are written.
This information is neatly presented in `G p' buffers for editing, so
I wondered if the code that does that, could be made to loop thru all
groups and print out a file with the group params info listed like in
`G p' buffers, but with a few additions like:
GROUPNAME
existing `G p' code ...
existing `G p' code ...
existing `G p' code ...
[...]
--
GROUPNAME
existing `G p' code ...
existing `G p' code ...
existing `G p' code ...
[...]
--
[...] and onward
And have this handy list written to a file.
I'm thinking of a batch command running this daily or as often as
seems necessary, and keeping some number of these generated files on
hand.
Sections could just be yanked into a `G p' buffer to re-establish
settings in the event of a problem.
So, I guess my question is first would such a looping construct,
using existing code and editing, be a major undertaking? Or is this
something a lisp impaired hacker could concoct with a little help?
And secondly, if this would be a good addition to gnus armaments.
Something along the lines of `nnml-generate-nov-data-bases'
(`gnus-generate-group-parameters-list') could then be batched easily by
anyone who is as careless as me.
Maybe a similar function (`gnus-generate--group-edit-list'), for `G E'
information.
next reply other threads:[~2001-02-26 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 16:27 Harry Putnam [this message]
2001-02-26 16:33 ` Paul Jarc
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=m3y9ut5s07.fsf@gnus.cvs.983032537 \
--to=reader@newsguy.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).