From: joaotavora@gmail.com (João Távora)
To: emacs-devel@gnu.org
Subject: Re: An easier way to edit variables
Date: Wed, 14 Jan 2015 15:37:28 +0000 [thread overview]
Message-ID: <jjblhl5jruv.fsf@gmail.com> (raw)
In-Reply-To: m2mw5l9yky.fsf@lifelogs.com
Ted Zlatanov <tzz@lifelogs.com> writes:
> 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.
Well, M-x customize can also "lose your data". I see your point, but
this is the point of the feature: change *any variable*, including
"dangerous" variables hidden from the user. Isn't that "disabled command
because new users find it confusing" feature used anymore?
> 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.
Why? Assume the user knows Lisp and use form, and pass it to READ.
Did you try my prototype?
> 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.
I've known about this, well, since the beginning, and of course I do use
it. But it still sucks to have to use
M-:
(setq find-the-variables-name-again )
Multiple C-x o to go to the *Help* window.
Scroll around until I find the form that I want to change.
Copy that to the kill ring
More C-x o
Yank it to the minibuffer
Remember to quote it, almost always
Perhaps I can cut down on some of these steps, but still, what Tom
proposes is way nicer.
next prev parent reply other threads:[~2015-01-14 15:37 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
2015-01-14 15:37 ` João Távora [this message]
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
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=jjblhl5jruv.fsf@gmail.com \
--to=joaotavora@gmail.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 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).