From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: On obsoleting defcustoms
Date: Fri, 13 Nov 2020 09:46:32 +0200 [thread overview]
Message-ID: <83ima9ya07.fsf@gnu.org> (raw)
In-Reply-To: <53945b2b-cb3f-4823-85e1-ff8676f10161@default> (message from Drew Adams on Thu, 12 Nov 2020 13:37:24 -0800 (PST))
> Date: Thu, 12 Nov 2020 13:37:24 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: emacs-devel@gnu.org
>
> But if it is, then why would it make any more sense to remove
> customization of an obsolete option that it would to remove
> advising an obsolete function or setting an obsolete defvar?
I didn't say we should remove customization of those, I said we should
not show them in the "customize group" buffer.
> If people are concerned about someone continuing to use
> something that's obsolete, why not just have Customize give
> a warning/message saying that the option is obsolete, and
> that the effect of changing its value is undefined?
We already say that, since we show the doc string.
> That's assuming that Emacs takes the (unusual, IME) point of
> view that, once declared obsolete, something should no longer
> be usable.
Not "usable", "used".
next prev parent reply other threads:[~2020-11-13 7:46 UTC|newest]
Thread overview: 26+ 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 21:37 ` On obsoleting defcustoms Drew Adams
2020-11-12 21:54 ` Stefan Kangas
2020-11-12 22:16 ` Drew Adams
2020-11-13 0:07 ` Stefan Kangas
2020-11-13 1:59 ` Drew Adams
2020-11-13 3:10 ` Stefan Kangas
2020-11-13 5:18 ` Drew Adams
2020-11-13 8:16 ` Eli Zaretskii
2020-11-13 7:46 ` Eli Zaretskii [this message]
2020-09-18 13:01 Stefan Kangas
2020-09-18 13:28 ` Eli Zaretskii
2020-09-18 13:40 ` Stefan Kangas
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ima9ya07.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.