From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: An easier way to edit variables
Date: Wed, 14 Jan 2015 10:22:21 -0500 [thread overview]
Message-ID: <m2mw5l9yky.fsf@lifelogs.com> (raw)
In-Reply-To: loom.20150113T224749-227@post.gmane.org
On Tue, 13 Jan 2015 21:53:52 +0000 (UTC) Tom <adatgyujto@gmail.com> wrote:
T> Ted Zlatanov <tzz <at> lifelogs.com> writes:
>>
>> The `describe-variable' popup already has a link to the customization
>> interface but the in-place-editing would be really nice. Perhaps it
>> could be implemented as an accordion-style interface (like in
>> `customize-group') so it's hidden by default, yet you don't need to hit
>> a link and go to a different buffer to use it.
>>
T> It should work for all variables, of course, not just for
T> customizable variables.
Perhaps, but I think it's significantly less useful to users if you just
drop them into a "enter a Lisp form" interface. It could actually be
harmful and lose their data.
T> I think it was pressing e for edit in the Help buffer, then
T> the buffer is narrowed to the variable value only (which can be a
T> complex list or anything) which you can modify in place and
T> then press C-c C-c to apply it to the variable and exit
T> edit mode.
...
T> That's why a quick edit feature in the Help buffer is useful, because
T> you already see the value there, so if it's complex list
T> (e.g. a font lock setting or anything) then you don't have to
T> copy it etc, if you just want to change one thing in it,
T> you just press e, you get the lisp value, you edit it,
T> press C-c C-c and it is applied instantly.
You'd need good custom editors for strings, lists, alists, plists... and
a guess on which one to use... and lots of luck :) IMHO it's better to
try to write customization tools that all users can use, and link to
those.
T> BTW, I should add that when I wrote "easier" in the subject I
T> meant easier for Lisp hackers who change Lisp variables on
T> a daily basis.
I really think those guys are in the minority and already know about
`setq` and `M-:` and so on. If you're targeting them specifically, it's
not as useful as I thought.
Ted
next prev parent reply other threads:[~2015-01-14 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 20:16 An easier way to edit variables Tom
2015-01-13 21:22 ` Ted Zlatanov
2015-01-13 21:53 ` Tom
2015-01-13 22:11 ` Tom
2015-01-14 15:20 ` João Távora
2015-01-14 16:36 ` Tom
2015-01-14 15:22 ` Ted Zlatanov [this message]
2015-01-14 15:37 ` João Távora
2015-01-14 15:54 ` an " Ivan Shmakov
2015-01-14 16:09 ` An " Tom
2015-01-14 16:56 ` Yuri Khan
2015-01-14 18:28 ` Tom
2015-01-14 19:10 ` Ted Zlatanov
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=m2mw5l9yky.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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 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.