unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Menu again.
Date: Thu, 24 Mar 2005 16:21:14 +0100	[thread overview]
Message-ID: <x53buloys5.fsf@lola.goethe.zz> (raw)
In-Reply-To: <4242D096.1050505@gnu.org> (Jason Rumney's message of "Thu, 24 Mar 2005 14:37:10 +0000")

Jason Rumney <jasonr@gnu.org> writes:

> David Kastrup wrote:
>
>>Now anybody with half a brain should be able to figure out that since
>>"this buffer" does not exist in the next Emacs session, there is
>>nothing to save here.  While in the long run, I don't think Emacs will
>>appeal to people without the ability to think straight, it might
>>perhaps be prudent to remove this particular option, which is the only
>>one that only applies to "this buffer" in the Options menu, as far as
>>I can see.
>>  
>>
> Its also one of the only options that I ever find the need to change
> once I've set up Emacs with my preferred options.

Of course.  Because you can't save this "preferred option".  All
options that you can save usually don't need changing once you set
them up.  I am not arguing that the option is without use, I am just
arguing that its presence in the Options menu, as a buffer-specific
option, in the position it is in, is confusing.  And that this
confusion has been cited to me in a Usenet group as an example that
Emacs does not offer a coherent user interface.

The order of "Save Options" and "Customize Emacs" is presumably
interchanged to make it clear to people that Customized options will
not get saved.  And neither is "Truncate Long Lines in this Buffer",
and it is right in the middle of the options that _are_ saved.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-24 15:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 14:11 Menu again David Kastrup
2005-03-24 14:37 ` Jason Rumney
2005-03-24 15:21   ` David Kastrup [this message]
2005-03-24 15:00 ` Luc Teirlinck
2005-03-24 15:32   ` David Kastrup
2005-03-24 15:55     ` Luc Teirlinck
2005-03-25 22:42       ` Kim F. Storm
2005-03-25 23:28         ` David Kastrup
2005-03-26  1:45         ` Nick Roberts
2005-03-26  1:28           ` David Kastrup
2005-03-26  2:15           ` Luc Teirlinck
2005-03-26  3:40             ` Blinking Cursor (was Re: Menu again.) Nick Roberts
2005-03-26 10:50               ` Blinking Cursor David Kastrup
2005-03-26 12:58                 ` Nick Roberts
2005-03-27  3:53               ` Blinking Cursor (was Re: Menu again.) Richard Stallman
2005-03-26  2:56         ` Menu again Luc Teirlinck
2005-03-26  8:16         ` Jan D.
2005-03-27  3:53         ` Richard Stallman
2005-03-25 22:44       ` Kim F. Storm
2005-03-26  2:18     ` Richard Stallman
2005-03-26 10:57       ` David Kastrup
2005-03-28 21:52         ` Kim F. Storm
2005-05-31  4:18 ` 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=x53buloys5.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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).