unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
	eliz@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Options menu
Date: Sun, 20 Mar 2005 22:40:31 +0100	[thread overview]
Message-ID: <x5sm2q808g.fsf@lola.goethe.zz> (raw)
In-Reply-To: <umzsyvyg2.fsf@jasonrumney.net> (Jason Rumney's message of "Sun, 20 Mar 2005 20:45:17 +0000")

Jason Rumney <jasonr@gnu.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> Since I have stared now at the current menus for 21.4 and 22.x for
>> longer than probably ever previously, I would like to mention one
>> other thing that has struck me as standing out negatively, and this
>> _would_ be a change with regard to 21.4: I'd swap the order of the
>> "Save Options" and "Customize Emacs" menu entries to make "Save
>> Options" be the last entry in the menu: that's where people look
>> for it.
>
> I think the reason to put it above "Customize Emacs" is to avoid
> misleading users into thinking that it will save changes made inside
> customize.
>
>> I am also not happy about the "Customize Emacs" menu name: it
>> implies that selecting options in the Options menu would be
>> different from customizing Emacs.  I'd prefer to have this menu
>> called "All Options"
>
> This has the same potential for misleading users about the scope of
> "Save Options".

Ok, now I know at least a potential reason for that arrangement.
Given that information, I am pretty much of the opinion that this
arrangement is fundamentally broken, and swapping the two menu entries
is a feeble attempt of conceiling it.  We won't fool anybody but
ourselves by that (well, we _will_ fool the users).

Putting "customize" off the "Options" menu altother does not appear
helpful (how about an unselectable entry "See also Tools/Customize"?),
so the only reasonably safe way I can think of is having "Save
Options" quip:

"Some Options have been set with Customize.  Save them too?"

as long as customized non-saved options remain.

Yes, this would make the proposed renaming of "Customize Emacs" into
"All Options" not the best idea.  However, "Customize Emacs" also does
not bring across the information that "Customize" is a special way of
customizing Emacs: the "Options" menu certainly is also used for
customizing Emacs.  So either we'd have to name this "Use Customize"
or "Customize" only, or "Customize Tool" (which would beg the question
why it is not in the "Tools" menu).

Swapping the menu entries alone (as is the reason for the current
arrangement) is far too obscure to help users figure that out.  In
addition, it will be a convenient shortcut for people playing around
with several customize options before they settle on an arrangement
they find fit for saving.

I am glad to hear that there is a reason for that strange order of
options, but I think the problem we are trying to solve that way
requires a less subtle approach.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-20 21:40 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18  8:54 Options menu Kim F. Storm
2005-03-18 10:31 ` David Kastrup
2005-03-18 12:57   ` Kim F. Storm
2005-03-18 14:58   ` Chong Yidong
2005-03-18 22:56   ` Lennart Borgman
2005-03-19 10:20     ` Eli Zaretskii
2005-03-19 11:24       ` David Kastrup
2005-03-19 15:32         ` Eli Zaretskii
2005-03-19 15:55           ` David Kastrup
2005-03-19 15:51       ` Lennart Borgman
2005-03-19 16:51         ` David Kastrup
2005-03-19 17:22         ` Eli Zaretskii
2005-03-19 18:18           ` Lennart Borgman
2005-03-20 12:59         ` Richard Stallman
2005-03-20 16:26           ` David Kastrup
2005-03-20 16:58             ` Luc Teirlinck
2005-03-20 17:31               ` David Kastrup
2005-03-20 17:43                 ` Luc Teirlinck
2005-03-20 18:06                   ` David Kastrup
2005-03-21  1:19                   ` Richard Stallman
2005-03-21  1:19                 ` Richard Stallman
2005-03-20 19:31             ` Lennart Borgman
2005-03-20 20:49               ` David Kastrup
2005-03-20 20:45             ` Jason Rumney
2005-03-20 21:40               ` David Kastrup [this message]
2005-03-20 22:27               ` Lennart Borgman
2005-03-20 23:10                 ` Luc Teirlinck
2005-03-21  0:02                   ` David Kastrup
2005-03-21  1:26                     ` Luc Teirlinck
2005-03-22  3:34                       ` Richard Stallman
2005-03-21  1:41                     ` Luc Teirlinck
2005-03-21  6:12                     ` Lennart Borgman
2005-03-21 23:28                       ` Luc Teirlinck
2005-03-21 23:35                         ` David Kastrup
2005-03-21 23:50                           ` Luc Teirlinck
2005-03-22  0:15                             ` David Kastrup
2005-03-22  6:20                               ` Lennart Borgman
2005-03-22 20:44                           ` Richard Stallman
2005-03-22 22:37                             ` David Kastrup
2005-03-20 22:12             ` Miles Bader
2005-03-18 15:48 ` Drew Adams
2005-03-18 20:30   ` Eli Zaretskii
2005-03-18 20:53     ` Drew Adams
2005-03-19 10:13       ` Eli Zaretskii
2005-03-19  3:08 ` Richard 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

  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=x5sm2q808g.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=rms@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).