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 23:04:54 -0500 (CDT)	[thread overview]
Message-ID: <200508010404.j7144s902996@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1DzOQk-0003tk-OJ@fencepost.gnu.org> (rms@gnu.org)

Richard Stallman wrote:

   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.

This is going to be very ugly when explained in the Emacs manual.  In
the Emacs manual you still will have to use (default-)indicate-empty-lines
and (default-)indicate-buffer-boundaries, because only they can be
given buffer local values (in the non default- version) and only they
can be set in .emacs (in the default- version).  Then you will have to
explain that to be able to safely use the default- versions, you have
to set the menu bar variable fringe-indicators to 'other, to avoid
having your customizations overridden by inadvertently loading fringe.el.

This is all unnecessarily complicated.

Sincerely,

Luc.

      parent reply	other threads:[~2005-08-01  4:04 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
     [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 [this message]

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=200508010404.j7144s902996@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).