GNU bug report logs - #5742
Customize and obsolete options

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 5742 in the body.
You can then email your comments to 5742 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #3 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: submit <at> debbugs.gnu.org
Subject: Customize and obsolete options
Date: Fri, 19 Mar 2010 20:44:44 -0400

Severity: wishlist

Customize does not seem to indicate in any way when options are
obsolete. Eg

emacs -Q -l diary-lib
C-h v diary-face

  This variable is obsolete since 23.1;
  customize the face `diary' instead.


But if I do

M-x customize-variable diary-face

there is no mention if it being obsolete.

I think it would be good to mention the obsolescence in the Customize
buffer in some way.


When browsing a group, eg with

M-x customize-group calendar-faces

it might be nice if the obsolete options were presented in a subdued
face if they had the default value (to indicate they should not be
customized), and perhaps in a more strident face if they had been
customized (to indicate that the user should check these settings and
perhaps migrate them to the newer way of doing things.)

Message #6 received at 5742 <at> debbugs.gnu.org (full text, mbox):

From: Jens Lechtenboerger <lechten <at> wi.uni-muenster.de>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 5742 <at> debbugs.gnu.org
Subject: Re: bug#5742: Customize and obsolete options
Date: Sat, 25 Mar 2017 18:07:28 +0100

On 2010-03-19, at 20:44, Glenn Morris wrote:

> Severity: wishlist
>
> Customize does not seem to indicate in any way when options are
> obsolete.
> [...]

I'd like to extend the reported issue.

Customize does not warn users of obsolete options.  This is
guaranteed to create surprises far in the future when the obsolete
feature is removed.  This is particularly bad, if no equivalent
functionality exists (or if it is not documented).  See bug#26233
for an example.

The functions custom-set-variables and customize-set-variable could
print warnings when they modify obsolete variables.

Even better, code that touches obsolete variables could generate
warnings.

Best wishes
Jens

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.