From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: contovob@tcd.ie, 23085@debbugs.gnu.org
Subject: bug#23085: 24.5; `customized-changed-options`
Date: Mon, 08 Feb 2021 17:15:05 +0200 [thread overview]
Message-ID: <83h7mmlhfq.fsf@gnu.org> (raw)
In-Reply-To: <87lfbznl8k.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 08 Feb 2021 07:10:03 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 23085@debbugs.gnu.org
> Date: Mon, 08 Feb 2021 07:10:03 +0100
>
> "Basil L. Contovounesios" <contovob@tcd.ie> writes:
>
> > I agree, but mostly just wanted to say that if customize-changed-options
> > is renamed, then its occurrences in code, docstrings, and the manual
> > should be updated, and the rename should probably be called out in NEWS.
>
> Definitely; I plumb forgot. (But Eli seems to think the change should
> be reverted
No, ignore me on that one: I thought the change was in the opposite
direction.
> -----
> @item M-x customize-changed @key{RET} @var{version} @key{RET}
> Set up a customization buffer with all the settings and groups
> whose meaning has changed since Emacs version @var{version}.
>
> @item M-x customize-changed-options @key{RET} @var{version} @key{RET}
> Set up a customization buffer with all the options whose meaning or
> default values have changed since Emacs version @var{version}.
> -----
>
> Which is wrong in any case, since they are aliases of each other.
Right.
next prev parent reply other threads:[~2021-02-08 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 22:45 bug#23085: 24.5; `customized-changed-options` Drew Adams
2016-03-27 0:43 ` John Wiegley
2021-02-07 14:07 ` Lars Ingebrigtsen
2021-02-07 15:26 ` Eli Zaretskii
2021-02-07 18:08 ` bug#23085: [External] : " Drew Adams
2021-02-07 20:47 ` Basil L. Contovounesios
2021-02-08 6:10 ` Lars Ingebrigtsen
2021-02-08 15:15 ` Eli Zaretskii [this message]
2021-02-09 7:20 ` Lars Ingebrigtsen
2021-02-08 6:05 ` Lars Ingebrigtsen
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=83h7mmlhfq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23085@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.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).