From: Mauro Aranda <maurooaranda@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 44598@debbugs.gnu.org
Subject: bug#44598: [PATCH] Do not show obsolete options in customize
Date: Thu, 12 Nov 2020 19:41:18 -0300 [thread overview]
Message-ID: <CABczVwey6+fFt6yo_1M6mY43hcMa-hKmZy4OOaDw54XESN2G6Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmm6p3OTSP5y5OFNoHTqxiQ7oysNYhPhLodxixqtD5KJZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
Stefan Kangas <stefan@marxist.se> writes:
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
>>> +*** Customize will no longer show obsolete user options.
>>> +
>>
>> Only when customizing a group, it seems. They still show up when using
>> customize-apropos (quite common), customize-saved (for an old setting,
>> it could be somewhat common), or when asking to customize them directly
>> (although that could be less common). I don't know what others think,
>> but perhaps customize-saved should still show them: after all, it is a
>> current user saved setting.
>
> Thanks, I overlooked that.
>
> I think `customize-option' and `customize-saved' should still show
> them, indeed.
>
> Excluding the above, is `customize-apropos' otherwise an exhaustive list
> of the commands where they would still be visible?
There's customize-changed-options too.
> I never use `customize-apropos', so what do you think makes sense for
> that command? Should it still show it?
To me, it makes sense that it follows what customize-group does, in this
regard.
>> Because of the above, perhaps it's too early to remove it?
>
> Perhaps, yes. I could just mention in its docstring that it's obsolete
> instead, since I can't find any facilities to mark a defface obsolete.
> Or maybe someone will enlighten me and tell me how it's done...
But if one Custom buffer still shows obsolete options, wouldn't the face
still be in use?
>> And the same goes for this: if the option is still likely to pop up in
>> some other Custom buffer, then this is useful information we might want
>> to keep showing to the user.
>
> Good point. I'll take a look at what happens with `customize-option' in
> particular, where we would want to mention that information.
Why not in the current place?
[-- Attachment #2: Type: text/html, Size: 2254 bytes --]
next prev parent reply other threads:[~2020-11-12 22:41 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
2020-11-12 21:44 ` Mauro Aranda
2020-11-12 22:08 ` Stefan Kangas
2020-11-12 22:41 ` Mauro Aranda [this message]
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=CABczVwey6+fFt6yo_1M6mY43hcMa-hKmZy4OOaDw54XESN2G6Q@mail.gmail.com \
--to=maurooaranda@gmail.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).