unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: customize option/variable
Date: Mon, 28 Aug 2023 20:23:56 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488BBE097C61DE5CBA9B56BF3E0A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <834jkjhvgw.fsf@gnu.org>

> > I am running emacs-29.1 on OpenBSD.
> >
> > Anytime I type M-x customize-option, as soon as I
> > start typing it changes from customize-option to
> > customize-variable.

If your minibuffer test that you start typing,
e.g., `customize-o' changes to `customize-variable'
then I think something in your init file or code it
loads is causing that.

I don't see that with `emacs -Q' (no init file).
Do you?

On the other hand, if what you mean is that after
you type `M-x customize-option RET' you see a
_prompt_ that says this:

  Customize variable: 

That's something different.  That's a prompt for
the name of the option.  A user option in Emacs is
a _customizable_ variable, that is, a variable that
you can change using the Customize system (UI or
functions).

Presumably, the reason the prompt says "variable"
and not option is to help underline the fact that
an option is a variable.

[Personally, I think it would be better for it to
say "Customize option:", to avoid the confusion you
encountered.  If someone doesn't know what an option
is then `C-h f customize-option' should tell them.]

> > Not knowing lisp, I would appreciate some assistance in correcting this.
> 
> There's no need to correct anything: an option in Emacs is also a
> variable.  IOW, these two are synonyms.

Not really, no.  Every option is a variable, but not
every variable is an option.  Of course, the command
has "customize" in its name, so yes, in this context,
every variable name you can usefully enter has to be
an option name.



      reply	other threads:[~2023-08-28 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 18:01 customize option/variable aalinovi
2023-08-28 18:29 ` Eli Zaretskii
2023-08-28 20:23   ` Drew Adams [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=SJ0PR10MB5488BBE097C61DE5CBA9B56BF3E0A@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).