all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 400@debbugs.gnu.org
Subject: bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Sun, 6 Sep 2020 10:13:28 -0700 (PDT)	[thread overview]
Message-ID: <ab146182-6e78-4ec9-801e-61da7b843ef1@default> (raw)
In-Reply-To: <<83o8mjnf5n.fsf@gnu.org>>

> > > emacs -Q
> > > M-x customize-option Info-hide-note-references
> > >
> > > Put the cursor on the unlispified option name:
> > > Info Hide Note References.
> > >
> > > C-h v
> > >
> > > The option name is not picked up as the default value.
> 
> I don't see how using "C-h v" in that case is a reasonable use case,
> since the documentation is displayed right below the name of the
> option.
> 
> We could perhaps have a help command that recognized names of
> variables in this format, but then it shouldn't be "C-h v", IMO, since
> that command talks about _variables_, whereas a name such as "Info
> Hide Note References" is not a variable name.

I said, "picked up as the default value".  Yes,
of course the unlispified name is typically not
itself a variable name.  But it's reasonable in
this context to provide the Lisp variable name
as a default value here, for `C-h v'.

As Kevin pointed out, `C-h v' provides not only
the doc string but links.

And this bug report is really more general, in
the sense that if we give Customize the inverse
function (get the Lisp name from the unlispified
name) then that can be used for more than just
`C-h v' - `describe-face', for instance.

The fact that `C-h v' output/behavior is similar
to what `customize-option' shows shouldn't get
in the way of seeing the utility of providing
a way to get the Lisp name from the unlispified
name.  That can be used beyond `C-h v'.





       reply	other threads:[~2020-09-06 17:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<007f01c8cca9$3cbbf770$c2b22382@us.oracle.com>
     [not found] ` <<875z8rum4k.fsf@gnus.org>
     [not found]   ` <<83o8mjnf5n.fsf@gnu.org>
2020-09-06 17:13     ` Drew Adams [this message]
2008-06-12 16:27 bug#400: 23.0.60; C-h v should pick up lispified name in Customize Drew Adams
2008-06-12 21:19 ` martin rudalics
2008-06-12 21:28   ` Drew Adams
2020-09-06 12:26 ` Lars Ingebrigtsen
2020-09-06 14:39   ` Eli Zaretskii
2020-09-06 16:33     ` Kévin Le Gouguec
2021-10-20 21:02     ` Stefan Kangas
2021-10-21  3:09       ` Lars Ingebrigtsen
2021-10-21  3:35         ` Stefan Kangas
2021-10-21  3:38           ` Lars Ingebrigtsen
2021-10-21 16:49             ` Stefan Kangas
2021-10-22 14:29               ` Lars Ingebrigtsen
2021-10-21  6:31       ` Eli Zaretskii
2021-10-21 15:47         ` Howard Melman
2021-10-21 17:02           ` Eli Zaretskii
2021-10-22  2:36             ` Howard Melman
2021-10-22  6:38               ` Eli Zaretskii
2021-10-22 15:38                 ` Howard Melman
2021-10-21 16:34         ` Stefan Kangas
2021-10-21 17:09           ` Eli Zaretskii
2021-10-21 17:50             ` Stefan Kangas
2021-10-21 18:00               ` Eli Zaretskii
2021-10-21 19:45                 ` Stefan Kangas
2021-10-22  6:05                   ` Eli Zaretskii
2021-10-22  8:12                     ` Stefan Kangas
2021-10-22 10:49                       ` Eli Zaretskii
2021-10-22  3:30           ` Howard Melman
2020-09-06 17:06   ` Drew Adams

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=ab146182-6e78-4ec9-801e-61da7b843ef1@default \
    --to=drew.adams@oracle.com \
    --cc=400@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 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.