unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: Options menu
Date: Fri, 18 Mar 2005 13:57:08 +0100	[thread overview]
Message-ID: <m3br9ht8m3.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <x5sm2ti6sh.fsf@lola.goethe.zz> (David Kastrup's message of "Fri, 18 Mar 2005 11:31:58 +0100")

David Kastrup <dak@gnu.org> writes:

>> OPTIONS
>> ======================================
>>    Customize Emacs                   >
>> --------------------------------------
>>    Language Environment (Mule)       >
>>    Set Font/fontset
>> --------------------------------------
>
> I don't think putting submenus at the top is a good idea, since the
> usual menu semantics imply that some of those menus tend to open in
> the process of trying to select options below them.

But the point of the rearrange is that those things are something
you use more often than the "one shot" options below it.  How
often do you toggle Syntax Highlighting?

> Customization menus tend to be at the bottom of menu stacks, anyway,
> for almost all applications I know.

I know, but on the Edit menu, or Tools menu -- and is called Options
or Preferences ... so it's still difficult to find.  Putting it at
the top of Options make it EASY to find.

>> [] Truncate Long Lines in this Buffer
>> [] Word Wrap in Text Modes
>> [] Case-insensitive Search
>> [] C-x/C-c/C-v cut-and-paste (CUA)
>
> The order of the above is completely arbitrary.  

Agree -- but it is the current order, I just don't have a better
proposal.

>> [] Use Directory Names in Buffer Names
>
> Looks like a candidate for "Appearance".  Appearance could be
> structured into overall appearance (frame stuff, cursor, menubar,
> toolbar, speedbar) and detailed appearance (dirnames in buffers, file
> name shadow, syntax highlighting).

I agree this would be a significant enhancement.

>
>> [] Save Places in Files between Sessions
>> [] Automatic File De/compression
>
> I'd remove the latter point from the menus and enable it by default.

Ok with me.

>
>> --------------------------------------
>> [] Enter Debugger on Error
>> [] Enter Debugger on Quit/C-g
>> --------------------------------------
>
> Not sure whether this is a good idea to put in a user menu.  It makes
> it somewhat easier to give instructions for generating backtraces in
> the case of tracking down a bug.  But it also is clutter.

For me, those are really the only options that I use regularly,
so removing them from Options may be ok if they are moved to
some other menu.

Perhaps they would fit better on the Help menu -- then then
you cannot save them (but do you really want to do that?)
I never want to save them, and was actually surprised to see
that they _are_ saved by "Save Options"!!!


>
>> Personally, I would also like to rename "Show/Hide" to "Appearence"
>> and move "Blinking Cursor" under that heading, but that's less
>> important.
>
> I think now that Emacs has a --no-blinking-cursor command line option
> that is also given by --help, those people that can't stand the cursor
> long enough to configure it off have a reasonable escape path.  So I'd
> move the Blinking Cursor to Appearance.  We should do what is
> reasonably possible to reduce clutter.

Agree.

  reply	other threads:[~2005-03-18 12:57 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 [this message]
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
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=m3br9ht8m3.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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).