From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mauro Aranda Newsgroups: gmane.emacs.bugs Subject: bug#44598: [PATCH] Do not show obsolete options in customize Date: Thu, 12 Nov 2020 19:41:18 -0300 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000fd2a9505b3f09c93" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1177"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 44598@debbugs.gnu.org To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Nov 12 23:42:21 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdLIK-0000Bi-Rk for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 12 Nov 2020 23:42:20 +0100 Original-Received: from localhost ([::1]:44212 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kdLIJ-0005Sd-O0 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 12 Nov 2020 17:42:19 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44988) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kdLI2-0005SP-QF for bug-gnu-emacs@gnu.org; Thu, 12 Nov 2020 17:42:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34389) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kdLI1-0002Cn-Qm for bug-gnu-emacs@gnu.org; Thu, 12 Nov 2020 17:42:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kdLI1-0001vt-Om for bug-gnu-emacs@gnu.org; Thu, 12 Nov 2020 17:42:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Mauro Aranda Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 12 Nov 2020 22:42:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44598 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 44598-submit@debbugs.gnu.org id=B44598.16052208997398 (code B ref 44598); Thu, 12 Nov 2020 22:42:01 +0000 Original-Received: (at 44598) by debbugs.gnu.org; 12 Nov 2020 22:41:39 +0000 Original-Received: from localhost ([127.0.0.1]:45935 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kdLHf-0001vG-H2 for submit@debbugs.gnu.org; Thu, 12 Nov 2020 17:41:39 -0500 Original-Received: from mail-wm1-f46.google.com ([209.85.128.46]:52822) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kdLHc-0001v3-UC for 44598@debbugs.gnu.org; Thu, 12 Nov 2020 17:41:38 -0500 Original-Received: by mail-wm1-f46.google.com with SMTP id 10so6586022wml.2 for <44598@debbugs.gnu.org>; Thu, 12 Nov 2020 14:41:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=9lEEfyBcoM8wkrgX87PR+bCBtT1CKAWE2d25ADcxL/8=; b=W4uUrjkIPCSbBDwxINQXHgcmS78OjodxxiKBtVRqql0oHwoTWByz4K7vDk57YqoL4J /czWleaQ/6BKU1vzqS+/AP/wLZmBdPB/7RRp2kMYQLULHr5vwRjgVc1qBEBnIg4JGcol FEOJK2jbORkNtPUF6BfMJ1C8wsr59bFHuPOi/EnUzV1aXdBHgTO7bQ2lHe+EUCnjr/7O AAeauiL5LCpw9iWcTx7d2Gs07Mbg273ocJyYHeydPM+NnukM+f3IWfPbTeLgrtfDDCPT syB1HtPffwphu8HPu/pasn2uvg3YJG2xp4BfH/BsP5L02sNgjIyCwC6V60VqU63Mxj22 3FvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9lEEfyBcoM8wkrgX87PR+bCBtT1CKAWE2d25ADcxL/8=; b=m2iTFj1m2dIYl/qoOZeYn2QMbUUFwHoDObPC8lCHEnPeFqvgStESSkHBYPx7kePHRk 72cmEhF2lRF8UK+Kt6HAzAkYIWZ/8BGTpfsBhJvkRUx6yYoRWFGWcF9LwUqqk3TITRgx ey+OFVnmXa+nflkdreIMB/oRiY/yg2ChtFWXERwVVcp0en8gXen0xdmRHrh40smkBTxn 2W11vymstxUuABpVSRCLc6CoCgFfNrxDeSEAA5DN6/8VGiaMvZe2kNgIs8nRKiB+yTyk 2jgApCcqRNXEB9obGOd/lrXXW340ECM0ZJcvlwdIvsMQ0zTPVBqnemZ6afehCB1BQKvG 8PWA== X-Gm-Message-State: AOAM532sWHC+k6KHsR6pm3KpdZHdjz+7Tx7k0En14j5zLP25Ia9iWqfs SxXoi6O/+YAZQQSiEusHV/ttxuxgnfe2iugMDV44IXUFDgg= X-Google-Smtp-Source: ABdhPJzzSlC1m/ECCCphEohGfl20fb+OIkfbXnzel0w0lIP4Hv6R6NlWpz3yE0Xm2pk3fW7KZEz/SLNjjCv3HXBMCFs= X-Received: by 2002:a1c:bac1:: with SMTP id k184mr66778wmf.76.1605220890911; Thu, 12 Nov 2020 14:41:30 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:193190 Archived-At: --000000000000fd2a9505b3f09c93 Content-Type: text/plain; charset="UTF-8" Stefan Kangas writes: > Mauro Aranda 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? --000000000000fd2a9505b3f09c93 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Stefan Kangas <ste= fan@marxist.se> writes:

> Mauro Aranda <maurooaranda@gmail.com> writes:
>>>> +*** Customize will no longer show obsolete user options.>>> +
>>
>> Only when customizing a group, it s= eems.=C2=A0 They still show up when using
>> customize-apropos (qu= ite common), customize-saved (for an old setting,
>> it could be s= omewhat common), or when asking to customize them directly
>> (alt= hough that could be less common).=C2=A0 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 `custom= ize-saved' should still show
> them, indeed.
>
> Excl= uding the above, is `customize-apropos' otherwise an exhaustive list> of the commands where they would still be visible?

There&= #39;s customize-changed-options too.

> I never = use `customize-apropos', so what do you think makes sense for
> t= hat command?=C2=A0 Should it still show it?

To me, it makes sense th= at it follows what customize-group does, in this
regard.

>>= Because of the above, perhaps it's too early to remove it?
>
= > Perhaps, yes.=C2=A0 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 h= ow it's done...

But if one Custom buffer still shows obsolete op= tions, wouldn't the face
still be in use?

>> And the sa= me goes for this: if the option is still likely to pop up in
>> so= me other Custom buffer, then this is useful information we might want
&g= t;> to keep showing to the user.
>
> Good point.=C2=A0 I'= ;ll take a look at what happens with `customize-option' in
> part= icular, where we would want to mention that information.

Why not in = the current place?
--000000000000fd2a9505b3f09c93--