unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23085@debbugs.gnu.org
Subject: bug#23085: 24.5; `customized-changed-options`
Date: Mon, 08 Feb 2021 07:05:26 +0100	[thread overview]
Message-ID: <87pn1bnlg9.fsf@gnus.org> (raw)
In-Reply-To: <83r1lrnbki.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 07 Feb 2021 17:26:37 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I'm not sure this change is for the better: no one said that "options"
> should be interpreted narrowly as referring only to variables; and
> "customize-changed" is simply bad English and doesn't help
> understanding what it is about.  So I think Richard was right with
> that change.

Richard added the (perhaps oddly named) `customize-changed' alias,
though.

I have no strong opinions about this, but we do usually refer to
defcustom'd variables as "user options", so it doesn't seem unreasonable
for a user to expect that `customize-changed-options' will list only
"user options" -- that seems like a natural expectation in this context,
even if "options" has a wider meaning outside a Customize context.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-02-08  6:05 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
2021-02-09  7:20           ` Lars Ingebrigtsen
2021-02-08  6:05     ` Lars Ingebrigtsen [this message]

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=87pn1bnlg9.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=23085@debbugs.gnu.org \
    --cc=eliz@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).