From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, ndame <emacsuser@freemail.hu>,
36826@debbugs.gnu.org
Subject: bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer
Date: Tue, 30 Jul 2019 11:53:29 -0700 (PDT) [thread overview]
Message-ID: <1aefceef-b0ae-4788-9734-80eb3fbbf7b3@default> (raw)
In-Reply-To: <8736iocgqp.fsf@web.de>
> > (`set-variable' does make the current value available
> > as the default (`M-n') for editing. In other respects
> > `customize-set-variable' is preferable to `set-variable'.)
>
> AFAICT: doesn't `customize-set-variable' prefill the minibuffer with
> the current value?
Seems to depend. For `fill-column', yes. For
`default-frame-alist' no. You get a hint at
the beginning of the prompt: "[repeat]", but
you have no idea what to repeat, no completion,
etc. You don't get the current value, as a
complex list etc., AFAICT. (I haven't checked
the code, to see what it really does.)
next prev parent reply other threads:[~2019-07-30 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:08 bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer ndame
2019-07-28 16:51 ` Drew Adams
2019-07-28 17:53 ` ndame
2019-07-28 18:01 ` Lars Ingebrigtsen
2019-07-29 4:00 ` Basil L. Contovounesios
2019-07-29 4:35 ` Drew Adams
2019-07-29 18:15 ` Juri Linkov
2019-07-29 13:55 ` Lars Ingebrigtsen
2019-07-29 14:18 ` Drew Adams
2019-07-29 4:28 ` Michael Heerdegen
2019-07-29 4:38 ` ndame
2019-07-29 14:22 ` Eli Zaretskii
2019-07-30 0:59 ` Michael Heerdegen
2019-07-30 2:43 ` Drew Adams
2019-07-30 4:02 ` Michael Heerdegen
2019-07-30 18:53 ` Drew Adams [this message]
2019-07-30 21:32 ` Michael Heerdegen
2019-07-29 4:46 ` Drew Adams
2022-04-17 17:00 ` Lars Ingebrigtsen
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=1aefceef-b0ae-4788-9734-80eb3fbbf7b3@default \
--to=drew.adams@oracle.com \
--cc=36826@debbugs.gnu.org \
--cc=emacsuser@freemail.hu \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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.