From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: Overlay arrow in *compilation* and *grep* buffers
Date: Mon, 25 Apr 2005 12:05:44 -0400 [thread overview]
Message-ID: <E1DQ65g-0005hG-Kq@fencepost.gnu.org> (raw)
In-Reply-To: <01c548ba$Blat.v2.4$e4827900@zahav.net.il> (eliz@gnu.org)
Notice the overlay arrow that covered part of the file name: this is a
bug, IMHO. If we want to have an arrow pointing out the current line,
we should indent the buffer text to the right as many columns as the
arrow string takes.
It might be good to do that when overlaying the arrow on a compilation
error buffer, but it would be a misfeature to do that when overlaying
the arrow on a program file (which was the original use of the overlay
arrow).
Perhaps we need a user option to
control these two features (scrolling and arrow) in a way that would
by default prevent scrolling when the arrow is used to show the
current line.
Also, the arrow feature is not customizable. What about users who
will dislike it and would wish to turn it off?
I'd probably prefer to turn off the arrow and use just the scrolling,
for compilation buffers.
next prev parent reply other threads:[~2005-04-25 16:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 10:45 Overlay arrow in *compilation* and *grep* buffers Eli Zaretskii
2005-04-24 18:42 ` Kim F. Storm
2005-04-24 20:04 ` Eli Zaretskii
2005-04-27 13:10 ` Kim F. Storm
2005-04-27 14:39 ` Eli Zaretskii
2005-04-28 11:01 ` Richard Stallman
2005-04-28 19:51 ` Eli Zaretskii
2005-04-28 20:54 ` Nick Roberts
2005-04-29 7:08 ` Eli Zaretskii
2005-04-29 8:52 ` Nick Roberts
2005-05-09 20:55 ` Juri Linkov
2005-05-10 6:40 ` David Kastrup
2005-05-12 11:38 ` Nick Roberts
2005-05-13 1:34 ` Richard Stallman
2005-05-13 5:03 ` Juri Linkov
2005-05-13 6:08 ` Eli Zaretskii
2005-05-13 7:18 ` Nick Roberts
2005-05-13 13:28 ` Eli Zaretskii
2005-05-14 0:26 ` Richard Stallman
2005-05-14 7:17 ` Eli Zaretskii
2005-05-14 22:20 ` Kim F. Storm
2005-05-15 15:58 ` Richard Stallman
2005-05-13 13:02 ` Nick Roberts
2005-05-14 0:25 ` Richard Stallman
2005-05-15 2:44 ` Nick Roberts
2005-05-15 4:12 ` Eli Zaretskii
2005-05-15 4:21 ` Eli Zaretskii
2005-05-15 22:39 ` Richard Stallman
2005-05-16 1:20 ` Nick Roberts
2005-05-16 19:28 ` Richard Stallman
2005-05-16 19:28 ` Richard Stallman
2005-05-16 22:16 ` Nick Roberts
2005-05-17 13:23 ` Richard Stallman
2005-04-29 10:49 ` Nick Roberts
2005-05-07 16:20 ` Eli Zaretskii
2005-05-07 21:10 ` Kim F. Storm
2005-05-08 0:41 ` Nick Roberts
2005-05-08 4:21 ` Eli Zaretskii
2005-05-08 5:49 ` Nick Roberts
2005-05-08 16:12 ` Richard Stallman
2005-05-08 19:37 ` Eli Zaretskii
2005-04-25 16:05 ` Richard Stallman [this message]
2005-04-25 16:46 ` Eli Zaretskii
2005-04-26 14:33 ` Richard Stallman
2005-04-28 11:34 ` Nick Roberts
2005-04-28 19:50 ` Eli Zaretskii
2005-04-28 21:16 ` Nick Roberts
2005-04-29 10:15 ` Richard Stallman
2005-04-29 12:19 ` Nick Roberts
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=E1DQ65g-0005hG-Kq@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).