all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 70212@debbugs.gnu.org
Subject: bug#70212: Customize Group buffer: add button to reveal underlying variable names
Date: Fri, 05 Apr 2024 15:27:22 +0300	[thread overview]
Message-ID: <86il0w5711.fsf@gnu.org> (raw)
In-Reply-To: <87jzlcmc3n.5.fsf@jidanni.org> (message from Dan Jacobson on Fri,  05 Apr 2024 16:45:48 +0800)

tags 70212 notabug
close 70212
thanks

> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Fri, 05 Apr 2024 16:45:48 +0800
> 
> The user is in buffer
> *Customize Group: Compilation* 
> 
> The user sees:
> Show Value Compilation Max Output Line Length 
>    Output lines that are longer than this value will be hidden. Hide
>    If nil, don’t hide anything.
> 
> Try as the user might, there is no way for him to discover the
> underlying variable there in the interface.

That's not how users are supposed to find out variable names.  The
Customize user interface is for users who don't need to know the Lisp
name of a variable.  You can customize this (and any other) variable
without knowing its Lisp name; forf all practical purposes its name is
"Compilation Max Output Line Length", which is written right there.
Which is why this UI doesn't mention the Lisp names of variables: they
might confuse users who don't know Lisp.

> All he can do is do C-h v and start guessing its name. Finally arriving at

The most efficient way of finding out the Lisp name of the variable is
to type:

  M-x apropos-variable RET Compilation Max Output Line Length RET

So I'm closing this bug as it is not a bug at all: Emacs behaves as
intended here.





  reply	other threads:[~2024-04-05 12:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  8:45 bug#70212: Customize Group buffer: add button to reveal underlying variable names Dan Jacobson
2024-04-05 12:27 ` Eli Zaretskii [this message]
2024-04-05 16:32   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-05 16:13 ` Juri Linkov
2024-04-05 16:47   ` Kévin Le Gouguec
2024-04-05 17:13     ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06  6:40       ` Dan Jacobson
2024-04-14 16:27 ` Howard Melman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86il0w5711.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70212@debbugs.gnu.org \
    --cc=jidanni@jidanni.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.