unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: default-indicate-buffer-boundaries
Date: Fri, 03 Feb 2006 00:05:24 -0500	[thread overview]
Message-ID: <E1F4t8O-0007Xk-7v@fencepost.gnu.org> (raw)
In-Reply-To: <200602020000.k1200mQ05508@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 1 Feb 2006 18:00:48 -0600 (CST))

    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.

    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.

These are pretty serious problems.

I am not willing to abandon such a nice feature without a fight!  We
do not need to fix this feature before the release, but does anyone
have an idea for how to fix it?

In the continuation case, we could solve the problem for the
end-of-buffer indicator by putting it on the right.  But that won't
help in the truncation case.

  reply	other threads:[~2006-02-03  5:05 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     ` default-indicate-buffer-boundaries Luc Teirlinck
2006-02-03  5:05       ` Richard M. Stallman [this message]
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

  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=E1F4t8O-0007Xk-7v@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).