bug#36832: Supply option to suppress scrolling in compilation mode buffers.

[Eli Zaretskii]

> Date: Tue, 30 Jul 2019 15:59:37 +0000
> Cc: 36832@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> > With this setting, how would the user know which error line is the
> > "current" one, whose source is displayed above?
> 
> Either by remembering it (she's just hit <CR> on it, after all), or by
> doing C-x o to move to that line, then C-x o to move back again.
> 
> The new option is intended for users who find being reminded of the
> current error line less important than being able to see the error lines
> above the current one "in context".
> 
> A possible modification would be to highlight the current line in the
> compilation mode buffer, but that's beginning to feel like a lot of work
> for a feature which might not really be wanted by anybody.

If this feature will not be wanted by anybody, why are we discussing
its addition?

I'm okay with adding the value you suggest if there will be some means
for delineating the current error line, either automatically when the
value t is in use or by an independent optional feature.

> This is an option, a non-default option, one which nobody is forced to
> use.  Having hacked it up a couple of days ago, I find it less stressful
> to use than the setting where the buffer jumps when I hit <CR> on it.

I understand, but I don't want us to introduce options that look like
we didn't think them through.