From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, 400@debbugs.gnu.org
Subject: bug#400: 23.0.60; C-h v should pick up lispified name in Customize
Date: Thu, 21 Oct 2021 09:31:34 +0300 [thread overview]
Message-ID: <83fssuany1.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkSm4OOsVJ1JNTd2qOdiGo-RCowHrsRhbz5C-tEN-FqvQ@mail.gmail.com> (message from Stefan Kangas on Wed, 20 Oct 2021 14:02:35 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 20 Oct 2021 14:02:35 -0700
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 400@debbugs.gnu.org, drew.adams@oracle.com
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > 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 appreciate the merits of this point of view, but at the same time it
> would be kind of nice with some DWIM here.
>
> I for one have gone through switching unlispify off, because it is
> faster to hit `C-h v RET' (firmly committed to muscle memory) than
> fiddling around with however it is you expand the documentation in a
> customize buffer; I guess the fastest way is C-a RET TAB TAB TAB (until
> point lands on "More") and then RET again.
??? The doc string is displayed by default, fully expanded. So why
would you need to "expand" it? What am I missing?
> So I think I would actually appreciate this feature, in particular if it
> was on `C-h v' because that's what I use everywhere else for variables.
> Even if it could perhaps be considered a bit "unclean".
Even if I'm missing something above, and you don't see the full doc
string by default, wouldn't it be better to have a special command in
the Custom buffer to expand the doc string, than tweak "C-h v" to do
something special in such cases?
next prev parent reply other threads:[~2021-10-21 6:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
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-20 21:27 ` bug#400: [External] : " Drew Adams
2021-10-21 6:37 ` Eli Zaretskii
2021-10-21 16:15 ` Drew Adams
2021-10-21 3:09 ` Lars Ingebrigtsen
2021-10-21 3:35 ` Stefan Kangas
2021-10-21 3:38 ` Lars Ingebrigtsen
2021-10-21 5:01 ` bug#400: [External] : " Drew Adams
2021-10-21 7:40 ` Eli Zaretskii
2021-10-21 16:49 ` Stefan Kangas
2021-10-22 14:29 ` Lars Ingebrigtsen
2021-10-22 17:13 ` bug#400: [External] : " Drew Adams
2021-10-21 4:26 ` Drew Adams
2021-10-21 7:36 ` Eli Zaretskii
2021-10-21 6:31 ` Eli Zaretskii [this message]
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-22 17:22 ` bug#400: [External] : " Drew Adams
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 16:56 ` bug#400: [External] : " Drew Adams
2021-10-22 3:30 ` Howard Melman
2021-10-22 16:51 ` bug#400: [External] : " Drew Adams
2021-10-23 18:25 ` Juri Linkov
2020-09-06 17:06 ` Drew Adams
[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
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=83fssuany1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=400@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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.