all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Visual cleanup for customize buffers
Date: Sun, 15 Jan 2006 22:19:17 -0600 (CST)	[thread overview]
Message-ID: <200601160419.k0G4JGv09689@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1EyGz2-0005hf-DT@fencepost.gnu.org> (rms@gnu.org)

Richard Stallman wrote:

   I suggest a different solution: don't allow hiding a setting that is
   in state "SET".

That would be bad, because unlike EDITED items, SET items can _start out_
hidden when the group is first visited.  If you unhide them, you
should be able to hide them again without warning.

There is _no way_ that these whole buffer buttons (in multi-option
buffers) can operate in a sensible way with respect to SET items,
hidden or not.  The user could have set these items using the menu bar
Options item or using `M-x customize-set-variable', without any intent
to save them (both mark the item SET).  But after quite a while, he
searches for another item, which, by coincidence, turns out to be in
the same group as one or more of the items he has set outside any
Custom buffer.  The group is huge, so he does not see this.  He saves
the one item he wants to save and inadvertently also saves the items
he only wanted to set temporarily.

The above is a way worse and way more likely problem than the user
hiding an option he has set with a state button.  Nobody knowing how
to use a State button is going to use the whole buffer buttons in
multi-option buffers anyway.  If they do, and they hid an item, it
most likely is because they did not want to save it, certainly if the
text above the whole buffer buttons clearly points out that HIDDEN
items will not be saved.

Just clearly stating above the whole buffer buttons that they do not
apply to HIDDEN items should, for now, eliminate user confusion about
hidden items.

Solving the other, more likely, problem I pointed out above could be
discussed after the release.

Maybe, after the release, it would be better to replace the current
set of six whole buffer buttons with three:

"Save Edited Items"  "Undo Edits"  "Kill buffer"

"Save Edited Items" is analogous to "Apply", "Kill Buffer" to "Cancel"
in other applications.  I do not believe that there is a need in Emacs
for the "OK" of other applications (which means "Save Edited Items and
Kill Buffer").

As the name says, "Save Edited Items" would only save EDITED items.  I
believe that this is a lot safer for beginning users who are likely to
have set items with the menu bar.  If they want to save items set with
the menu bar, they should use "Save Options" from the Menu bar.  If
they want to save items they have set with a State button, they should
save them with the State button.  If the whole buffer buttons _only_
affect EDITED items, then there is no problem with hidden options,
because EDITED items can not be HIDDEN.

Sincerely,

Luc.

  reply	other threads:[~2006-01-16  4:19 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 21:58 Visual cleanup for customize buffers Kim F. Storm
2006-01-12 23:45 ` Luc Teirlinck
2006-01-13 12:37   ` Kim F. Storm
2006-01-13 14:18     ` Luc Teirlinck
2006-01-13 15:16       ` Kim F. Storm
2006-01-13 19:05         ` Drew Adams
2006-01-13 19:16         ` David Kastrup
2006-01-13 23:28         ` Luc Teirlinck
2006-01-13 23:34           ` Luc Teirlinck
2006-01-14 16:14           ` Richard M. Stallman
2006-01-14  0:08         ` Luc Teirlinck
2006-01-14  0:44         ` Luc Teirlinck
2006-01-14  1:56           ` Kim F. Storm
2006-01-14  2:58             ` Chong Yidong
2006-01-14  6:10             ` Drew Adams
2006-01-14 16:14           ` Richard M. Stallman
2006-01-14 16:14         ` Richard M. Stallman
2006-01-14 20:50           ` Lennart Borgman
2006-01-14 21:32             ` Luc Teirlinck
2006-01-14 21:47               ` Lennart Borgman
2006-01-15 18:09                 ` Luc Teirlinck
2006-01-15 18:41                 ` Kim F. Storm
2006-01-15 19:59                   ` Luc Teirlinck
2006-01-14 21:58           ` Drew Adams
2006-01-14 22:17             ` Drew Adams
2006-01-15  1:40           ` Luc Teirlinck
2006-01-15 23:08             ` Richard M. Stallman
2006-01-16  4:19               ` Luc Teirlinck [this message]
2006-01-19 17:44                 ` Richard M. Stallman
2006-01-17  4:20               ` Luc Teirlinck
2006-01-17 20:00                 ` Richard M. Stallman
2006-01-20  0:18                   ` Luc Teirlinck
2006-01-13 16:40     ` Stefan Monnier
2006-01-13 19:04   ` Bill Wohler
2006-01-14  1:28     ` Luc Teirlinck
2006-01-14  1:46       ` Bill Wohler
2006-01-14  5:49   ` Richard M. Stallman
2006-01-14 15:28     ` Luc Teirlinck
2006-01-13  0:08 ` Luc Teirlinck
2006-01-13 15:24   ` Kim F. Storm
2006-01-13 19:33     ` martin rudalics
2006-01-13  0:24 ` Luc Teirlinck
2006-01-14  5:48   ` Richard M. Stallman
2006-01-14  5:49 ` Richard M. Stallman
2006-01-14 15:07   ` Luc Teirlinck
2006-01-14 23:05   ` Luc Teirlinck
2006-01-15  4:40     ` Luc Teirlinck
2006-02-05  0:07     ` Kim F. Storm
2006-02-06  2:07       ` Richard M. Stallman
2006-02-06  4:30       ` Luc Teirlinck
2006-02-06  7:21         ` Eli Zaretskii
2006-02-06 17:35           ` Luc Teirlinck
2006-01-14 23:27   ` Luc Teirlinck
2006-01-14 23:45     ` Drew Adams
2006-01-15 18:59     ` Kim F. Storm
2006-01-15  4:17   ` Luc Teirlinck
2006-01-15 23:08     ` Richard M. Stallman

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=200601160419.k0G4JGv09689@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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.