unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: unnecessary fringe-indicators defcustom creates trouble
Date: Fri, 29 Jul 2005 23:02:41 -0500 (CDT)	[thread overview]
Message-ID: <200507300402.j6U42fG22278@raven.dms.auburn.edu> (raw)
In-Reply-To: <m364utk4vm.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

Kim Storm wrote:

   Fine with me, but others may object to removing the ability to set the
   indicators from the menu bar...

My patches do not _preclude_ re-adding them to the menubar.  But since
we can not possibly add _all_ options to the menu bar (to avoid people
ever having to use Custom), it would seem that the most important
criteria for adding an option to the menubar are that it either should
be something that many users would want to set straight when they
begin using Emacs, before having read any documentation (like say,
disabling the blinking cursor) or something that people might want to
change several times during a session.  indicate-buffer-boundaries
fits neither criterion.

Enabling a user to set all possible 81 values of indicate-buffer-boundaries
through the menu bar is possible, but would be rather elaborate.
Allowing to set only a subset of the possible values through the
menubar might give problems when trying to indicate which value is
enabled in the menubar, if the user chose another value in some other way.

The option did not exist in 21.4, so it never was customizable through
the menubar in any released version.  It is a complex option and hence
is better customized through Custom.

Sincerely,

Luc.

  reply	other threads:[~2005-07-30  4:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29  1:13 unnecessary fringe-indicators defcustom creates trouble Luc Teirlinck
2005-07-29 15:29 ` Kim F. Storm
2005-07-30  4:02   ` Luc Teirlinck [this message]
2005-08-01  0:45 ` Richard M. Stallman
2005-08-01  2:47   ` Luc Teirlinck
2005-08-01 16:45     ` Richard M. Stallman
     [not found]       ` <200508012118.j71LI0N06793@raven.dms.auburn.edu>
2005-08-02 17:44         ` Richard M. Stallman
2005-08-02 20:31           ` Luc Teirlinck
2005-08-03 19:09             ` Richard M. Stallman
2005-08-04  1:03               ` Luc Teirlinck
2005-08-04  2:49                 ` Luc Teirlinck
2005-08-06 18:36                   ` Richard M. Stallman
2005-08-06 18:36                 ` Richard M. Stallman
2005-08-01  4:04   ` Luc Teirlinck

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=200507300402.j6U42fG22278@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).