From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: unnecessary fringe-indicators defcustom creates trouble
Date: Mon, 01 Aug 2005 12:45:53 -0400 [thread overview]
Message-ID: <E1DzdQH-0008MD-M1@fencepost.gnu.org> (raw)
In-Reply-To: <200508010247.j712l3B02940@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 31 Jul 2005 21:47:03 -0500 (CDT))
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?
Because they are more complex. This is simple.
It is meant for less experienced users.
You would also need to change the Emacs
manual
If you tell me precisely where, I will do that.
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'.
To avoid small problem risks like that is probably impossible.
It would not be worth making a major change because of this.
Can you think of nay small change to avoid this risk?
next prev parent reply other threads:[~2005-08-01 16:45 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
2005-08-01 16:45 ` Richard M. Stallman [this message]
[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=E1DzdQH-0008MD-M1@fencepost.gnu.org \
--to=rms@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).