From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, 44598@debbugs.gnu.org
Subject: bug#44598: [PATCH] Do not show obsolete options in customize
Date: Thu, 12 Nov 2020 13:40:56 -0800 (PST) [thread overview]
Message-ID: <13e33f86-16c2-4833-b6b0-3e14d8e694cb@default> (raw)
In-Reply-To: <CADwFkmm4FUU8RRArBi2u_WOgM=PoYgtiuC-bgETe7X2jOiCWvQ@mail.gmail.com>
> In a recent discussion on emacs-devel,[1]
Wow. I missed that. I've responded there now.
> > IMO, we shouldn't show obsolete options at all in a Custom buffer,
> > for the same reason why we remove them from the manuals.
>
> How about the attached patch?
FTR, I disagree with this approach. I think it hurts
more than it helps.
If customizing some _particular_ option has a very
negative effect, then it could be dealt with specially.
But to just remove customization of all obsolete options
makes no sense to me. And "for the same reason" as not
documenting something that's obsolete doesn't sound like
a sound reason to me, at all. Doc is one thing. Use is
another.
next prev parent reply other threads:[~2020-11-12 21:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADwFkmm2G=OPOdgadhDk+1uCbHzuqpqaYDs1KgdDes7gXLYgxg@mail.gmail.com>
[not found] ` <83lfh743j8.fsf@gnu.org>
2020-11-12 20:56 ` bug#44598: [PATCH] Do not show obsolete options in customize Stefan Kangas
2020-11-12 21:11 ` Basil L. Contovounesios
2020-11-12 21:39 ` Stefan Kangas
2020-11-12 22:18 ` Basil L. Contovounesios
2020-11-13 7:43 ` Eli Zaretskii
2020-11-12 21:40 ` Drew Adams [this message]
2020-11-12 21:44 ` Mauro Aranda
2020-11-12 22:08 ` Stefan Kangas
2020-11-12 22:41 ` Mauro Aranda
2020-11-13 7:48 ` Eli Zaretskii
2020-11-13 7:40 ` Eli Zaretskii
2020-11-13 17:10 ` Stefan Kangas
2020-11-14 14:22 ` Eli Zaretskii
2020-11-20 13:37 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13e33f86-16c2-4833-b6b0-3e14d8e694cb@default \
--to=drew.adams@oracle.com \
--cc=44598@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).