From: Jack Twilley <jmt+usenet@tbe.net>
Subject: Suggestion: gnus variable checker thing
Date: 03 Jan 2001 22:06:51 -0800 [thread overview]
Message-ID: <m3itnvdf5w.fsf@duchess.twilley.org> (raw)
I don't know the right words to explain what I want, so I'm going to
try and it's going to come out funny, so please don't laugh. :-)
A few times I've been caught by upgrades where I've had an "old"
variable in my .gnus or .emacs that did something, and then Gnus
changed from underneath me, and then I had to spend a long time fixing
it.
Any way we could have some kind of automatic thing that checked for
the setting of certain variables and tossed out warnings that said
something like:
*** gnus-foo is deprecated, use gnus-article-bar instead ***
Hopefully the general point of what I'm trying to express will come
out more clearly than this description reads.
Jack.
(I'm sober, too...)
--
Jack Twilley
jmt at tbe dot net
http colon slash slash www dot tbe dot net slash tilde jmt slash
reply other threads:[~2001-01-04 6:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3itnvdf5w.fsf@duchess.twilley.org \
--to=jmt+usenet@tbe.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).