From: Eli Zaretskii <eliz@gnu.org>
To: ndame <emacsuser@freemail.hu>
Cc: michael_heerdegen@web.de, larsi@gnus.org, 36826@debbugs.gnu.org
Subject: bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer
Date: Mon, 29 Jul 2019 17:22:14 +0300 [thread overview]
Message-ID: <83v9vkkjjd.fsf@gnu.org> (raw)
In-Reply-To: <Axuu0g.HkCXWWtfWbR.MB54p8XYTOQqsLkRnbS@freemail.hu> (message from ndame on Mon, 29 Jul 2019 04:38:25 +0000 (GMT))
> Date: Mon, 29 Jul 2019 04:38:25 +0000 (GMT)
> From: ndame <emacsuser@freemail.hu>
> Cc: "36826@debbugs.gnu.org" <36826@debbugs.gnu.org>
>
> > - It is no fun for variables with complicated values, like large lists
> of lists. Just a minibuffer prompt would not be nice.
>
> That's why I mentioned popup buffers for complicated values. It could
> be especially useful for variables with complicated values like nested
> lists. You just press e, a buffer pops up with the value, so you don't have
> to manually copy it to scratch, etc. you can tweak it in place quickly and
> set it with C-c C-c
Would invoking Customize with 'e' fix most of the problems?
next prev parent reply other threads:[~2019-07-29 14:22 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 [this message]
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
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
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=83v9vkkjjd.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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).