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: Sun, 31 Jul 2005 21:47:03 -0500 (CDT)	[thread overview]
Message-ID: <200508010247.j712l3B02940@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DzOQk-0003tk-OJ@fencepost.gnu.org> (rms@gnu.org)

Richard Stallman wrote:

   The reason for this is to make it simple to request the usual options.

I do not see why you need a separate variable for that.  Why can one
not use indicate-empty-lines and indicate-buffer-boundaries to do
that?  Actually, I believe that the one option that makes sense for
most people is to set indicate-empty-lines to t (which my patches
allow to do via the menu bar).  But if for some reason that would not
be sufficient (for the menu bar) one could always (for instance)
change the current three non-alist values of
`indicate-buffer-boundaries' (left, right, other non-nil symbol) to
the values used by `fringe-indicators' (left, right, box, mixed),
thereby making fringe-indicators unnecessary, even for current
menu-bar functionality.

   But I agree it shouldn't get in the way of setting the other variables
   directly, if you want to do that.  So I propose this change.
   (I will also change the doc strings of default-indicate-empty-lines
   and default-indicate-buffer-boundaries.)

Still looks very unnatural and contorted to me.  But if you are going
to do it that way, then the docstring of fringe-indicators should say
that setting it to a value different from 'other outside Custom (or
the menu bar) does not work.  You would also need to change the Emacs
manual and the `default-indicate-empty-lines' docstring.

Another problem is that the first line of the indicate-empty-lines
docstring is pretty self-explanatory.  So somebody setting this
through Custom may not click on MORE and see the warning about first
setting fringe-indicators to 'other.

Sincerely,

Luc.

  reply	other threads:[~2005-08-01  2:47 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
2005-08-01  0:45 ` Richard M. Stallman
2005-08-01  2:47   ` Luc Teirlinck [this message]
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=200508010247.j712l3B02940@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).