Re: current compile.el issues

[Stefan Monnier]

> Obviously developers don't agree with most of this, but I guess other
> users and providers of add-ons will:

Your notion of obviousness seems skewed ;-)
Lack of implementation should not be taken as a sign that developers don't
want a feature.

>  * I think `compilation-context-lines' should default to 0, per
>    previous behaviour.  That way you can tell what the current error
>    line is.

Several people have asked for that.  I have no preference and it's just
a change of the default value of a variable, so anybody can do it.

>  * I find the highlighting of output files distracting when looking
>    for errors in the output, but `compilation-mode-font-lock-keywords'
>    isn't customizable to turn it off.

Are you referring to the `face' or the `mouse-face' property?
I agree there should be a way to turn off the `face' property in
compilation buffers.  I hadn't thought about the `mouse-face' property yet
and am not sure what to think of it.

>  * Since (I guess) there's no way to limit the region parsed for
>    errors now, C-x ` doesn't work the way it used to in Lisp
>    *Compile-Log* buffers -- you get the first error in the buffer, not
>    the first from the last compilation.  The lack of the
>    `compilation-parsing-end' facility is also a serious annoyance for
>    dealing with errors from evaluations in a Comint buffer.

This is a bug I'm working on.

>  * Moving to errors in compilation-shell-minor-mode shifts point
>    around so that it's no longer at the prompt -- I think it should
>    just alter the window, if that's necessary to display the error
>    message.

By "moving to errors" you mean "with C-x ` or somesuch", right?
Sounds like a bug indeed, although more minor.

>  * I still don't know what the proper definition of `informational'
>    messages is, since messages can be highlighted with
>    `compilation-info-face' when compilation-skip-threshold's value is 1.

I don't understand this.  Maybe Daniel can help.


        Stefan