unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: On obsoleting defcustoms
Date: Thu, 12 Nov 2020 16:54:44 -0500	[thread overview]
Message-ID: <CADwFkmmdH9geMXj+u7Pgvo72JJ3_M5NZZjE3Qvfm=tuvdKJAgw@mail.gmail.com> (raw)
In-Reply-To: <53945b2b-cb3f-4823-85e1-ff8676f10161@default>

[[ For context, I have just filed this bug:
   bug#44598: [PATCH] Do not show obsolete options in customize ]]

Drew Adams <drew.adams@oracle.com> writes:

> 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

That's what we do now.  See `M-x customize-group RET browse-url RET' in
Emacs 27 for a bad case of what that might look like.

> That's assuming that Emacs takes the (unusual, IME) point of
> view that, once declared obsolete, something should no longer
> be usable.

It's still usable with the patch, just not advertised.



  reply	other threads:[~2020-11-12 21:54 UTC|newest]

Thread overview: 12+ 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 [this message]
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
2020-09-18 13:01 Stefan Kangas
2020-09-18 13:28 ` Eli Zaretskii
2020-09-18 13:40   ` 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='CADwFkmmdH9geMXj+u7Pgvo72JJ3_M5NZZjE3Qvfm=tuvdKJAgw@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).