unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ndame <emacsuser@freemail.hu>, 36826@debbugs.gnu.org
Subject: bug#36826: 26.1; request: add variable value editing feature to the *Help* buffer
Date: Mon, 29 Jul 2019 06:28:36 +0200	[thread overview]
Message-ID: <87a7cx4g7f.fsf@web.de> (raw)
In-Reply-To: <m3h8763uon.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 28 Jul 2019 20:01:12 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I think this sounds useful.  I'm often rooting around not quite sure
> what variable I'm looking for in the help buffers, and trying
> different values, and having a command to make this faster would be
> nice.  There's `customize-variable', but I...  just don't like it.
> (And besides, not all variables are customisable...)

There are also some downsides:

- Changing variables might break Emacs if you are not knowing what you
are doing.  Customize at least has some safety checks.  Users might not
expect that clicking on the button and changing values might have
dangerous consequences.  Likewise, Emacs might change or modify the
value and users wonder why their setting had been "rejected".  With
other words: it is potentially dangerous and might confuse users.

- It is no fun for variables with complicated values, like large lists
of lists.  Just a minibuffer prompt would not be nice.  Here you
probably still would use scratch or so.  And even in the situation you
described, I would prefer having an expression in scratch, edit and eval
it, compared to clicking a button in the help buffer and edit in the mb
or a popup buffer.

- There are nitpicks which may complicate doing what at first sounds
simple, e.g. what if the value includes things were printing and reading
comes into play?  E.g. buffers: they have a print syntax, but it's not a
read syntax.  Objects may be replaced by equal objects (e.g. lists will
be recreated) which might confuse Emacs.  There is buffer local
vs. global bindings of variables (and hooks), etc.

But my main point is the question if we should really invite the typical
user, which is not an Emacs developer (ok, here I'm not really sure if
I'm right) to change variables on the fly, or if it's not better if
these users are directed to customize, and the others use just M-: or
ielm or what they use now.

Michael.





  parent reply	other threads:[~2019-07-29  4:28 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 [this message]
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
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=87a7cx4g7f.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=36826@debbugs.gnu.org \
    --cc=emacsuser@freemail.hu \
    --cc=larsi@gnus.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).