From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: default-indicate-buffer-boundaries
Date: Wed, 1 Feb 2006 18:00:48 -0600 (CST) [thread overview]
Message-ID: <200602020000.k1200mQ05508@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1F4Npr-0000Xw-5Y@fencepost.gnu.org> (rms@gnu.org)
Richard Stallman wrote:
When I tried out `left' and various other settings for
indicate-buffer-boundaries, I found it messy and confusing, because it
more or less at random can either hide other marks in the fringe or be
hidden by them.
Can you provide a test case?
Do `emacs -q' and set indicate-buffer-boundaries to 'left.
Hold your finger on the `1' key until you get a continuation line.
Note that the indicate-buffer-boundaries glyph overrides the
continuation glyph that would normally appear in the left margin.
The right continuation glyph is still visible. But do `M-0 C-l'
and it is out of view, leaving no indication that this is a
continuation line. But "fixing" this so that the continuation glyph
overrides the indicate-buffer-boundaries glyph would probably be worse.
Now do `M-x toggle-truncate-lines' (with point still at the end of the
long line). Now all indicate-buffer-boundaries glyphs are overridden
by the truncation arrows. But "fixing" this so that the
indicate-buffer-boundaries glyphs override the truncation arrows would
be worse.
I believe to remember that some other Emacs features put glyphs in the
fringe, although I do not immediately remember the details. Similar
problems occur for them: obviously, they either have to override the
indicate-buffer-boundaries glyphs, or be overridden by them.
It is a while ago that I played around with indicate-buffer-boundaries,
so I do not remember the exact details, but I remember that the
problems were, in my usage, bad enough that I had to decide to reset
it to nil and use `indicate-empty-lines' instead.
`indicate-empty-lines' works well with continuation lines, truncated
lines and other Emacs features that use the fringe. It only puts
glyphs in the fringe of empty lines, so it does not compete with
anything else.
Sincerely,
Luc.
next prev parent reply other threads:[~2006-02-02 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 18:06 default-indicate-buffer-boundaries Richard M. Stallman
2006-01-31 19:25 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-01 19:40 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-02 0:00 ` Luc Teirlinck [this message]
2006-02-03 5:05 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-03 5:16 ` default-indicate-buffer-boundaries Miles Bader
2006-02-03 9:12 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-04 18:25 ` default-indicate-buffer-boundaries Richard M. Stallman
2006-02-03 9:10 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-03 18:20 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-04 0:33 ` default-indicate-buffer-boundaries Miles Bader
2006-02-04 12:19 ` default-indicate-buffer-boundaries Robert J. Chassell
2006-02-05 0:57 ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-06 7:52 ` default-indicate-buffer-boundaries Juri Linkov
2006-02-01 23:37 ` default-indicate-buffer-boundaries Kim F. Storm
2006-02-02 1:46 ` default-indicate-buffer-boundaries Miles Bader
2006-02-02 2:29 ` default-indicate-buffer-boundaries 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602020000.k1200mQ05508@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.