From: Howard Melman <hmelman@gmail.com>
To: 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 23:30:33 -0400 [thread overview]
Message-ID: <ly4k99g2hy.fsf@new-host-2.home> (raw)
In-Reply-To: <007f01c8cca9$3cbbf770$c2b22382@us.oracle.com>
Stefan Kangas <stefan@marxist.se> writes:
> A special command to expand would be useful, I think.
>
> But users might still want an easy way to get the variable into the help
> buffer. For example, they might be using helpful.el that displays all
> kinds of additional information in that buffer, or they might just
> prefer having a separate buffer to display the documentation. I'm in
> the latter camp; expanding documentation on the customize screen itself
> makes it harder to get an overview of all available options, so I often
> would rather put the full length docstring in a separate buffer.
FWIW I'd like a command in a customize-group buffer to
expand all docstrings. When I try out a new package I often
use customize-group to get an overview of things I can tweak
in it, and it's a pain to click More on all the options and
to open them.
bug#15748 "Provide a way to hide/show all values" is for
this, but I'm now thinking that something like outline-cycle
would be great in any customize buffer. Let S-TAB cycle
through the various states of all options at once.
--
Howard
next prev parent reply other threads:[~2021-10-22 3:30 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
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 [this message]
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
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=ly4k99g2hy.fsf@new-host-2.home \
--to=hmelman@gmail.com \
--cc=400@debbugs.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).