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: Options menu
Date: Fri, 18 Mar 2005 11:31:58 +0100	[thread overview]
Message-ID: <x5sm2ti6sh.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3sm2t5o70.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Fri, 18 Mar 2005 09:54:27 +0100")

storm@cua.dk (Kim F. Storm) writes:

> With the recent addition of "blinking cursor" to the options
> menu, it has become even more dis-organized than before.
>
>
> I suggest to rearrange it slightly to make the structure
> more logical and useful, by placing frequently used
> items at the top and "one-time" customizations later.

Uh, that's not "logical", that is at best "useful", and for a doubtful
value of "useful": after all, a logical grouping will save people time
also by letting them skip over uninteresting sections.

> OPTIONS
> ======================================
>    Customize Emacs                   >
> --------------------------------------
>    Language Environment (Mule)       >
>    Set Font/fontset
> --------------------------------------
>    Show/Hide                         >
> [] Blinking Cursor
> [] Syntax Highlighting
> [] Paren Match Highlighting
> [] Active Region Highlighting
> --------------------------------------

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.

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


> [] 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.  We have some
highlighting stuff, then we have the buffer-specific long line stuff,
then we have some formatting specific "in text modes", then comes a
completely unrelated search option, and then again an editing mode
speciality.

This is pretty much chaotic.

> [] 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).

> [] Save Places in Files between Sessions
> [] Automatic File De/compression

I'd remove the latter point from the menus and enable it by default.

> --------------------------------------
> [] 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.

> 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.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-18 10:31 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 [this message]
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
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=x5sm2ti6sh.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).