From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 36832@debbugs.gnu.org
Subject: bug#36832: Supply option to suppress scrolling in compilation mode buffers.
Date: Wed, 31 Jul 2019 17:21:49 +0300 [thread overview]
Message-ID: <83ef26i8si.fsf@gnu.org> (raw)
In-Reply-To: <20190730193235.GE5427@ACM> (message from Alan Mackenzie on Tue, 30 Jul 2019 19:32:35 +0000)
> Date: Tue, 30 Jul 2019 19:32:35 +0000
> Cc: 36832@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> The current code does two things, sometimes, on <CR> being hit: (i) it
> puts an indicator into the fringe; (ii) it scrolls the compile mode
> window upwards, the pertinent line moving either to the top, or to a
> specified window line.
>
> Unfortunately, the code which does these things seems to be fragmented,
> and there is just one user option to control (i) and (ii) above.
>
> One solution would be always to mark to the line in the compile mode
> window, whether by an indicator in the fringe or a ">" or "=>" at column
> 0. Then only scroll the compile mode window when the user has explicitly
> requested this by the user option compilation-context-lines.
Yes, that would be an okay solution.
> Why do these little things so often turn out to be so complicated? ;-(
;-)
next prev parent reply other threads:[~2019-07-31 14:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 20:32 bug#36832: Supply option to suppress scrolling in compilation mode buffers Alan Mackenzie
2019-07-30 15:14 ` Eli Zaretskii
2019-07-30 15:59 ` Alan Mackenzie
2019-07-30 16:17 ` Eli Zaretskii
2019-07-30 19:20 ` Juri Linkov
2019-07-31 14:20 ` Eli Zaretskii
2019-07-30 19:32 ` Alan Mackenzie
2019-07-31 14:21 ` Eli Zaretskii [this message]
2019-08-25 10:32 ` Alan Mackenzie
2019-09-01 21:50 ` Mattias Engdegård
[not found] ` <handler.36832.B.156434595120203.ack@debbugs.gnu.org>
2019-09-03 17:44 ` Alan Mackenzie
2019-09-04 12:41 ` Mattias Engdegård
2019-09-05 17:50 ` Alan Mackenzie
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=83ef26i8si.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36832@debbugs.gnu.org \
--cc=acm@muc.de \
/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.