[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: current compile.el issues

From: Miles Bader
Subject: Re: current compile.el issues
Date: Tue, 27 Apr 2004 18:32:00 -0400
User-agent: Mutt/1.3.28i

On Tue, Apr 27, 2004 at 11:13:45PM +0200, Daniel Pfeiffer wrote:
> > >  * 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 think doing this the same way as scrolling is a good idea, but I can always
> set this option if it defaults to 0.  This is however the first request since
> the fringe arrow appeared, so I don't know if many people still want this.

I think the fringe arrow is a clever idea, but I find that in use it doesn't
work very well -- it's still too hard for my eye to locate, I often still
have to conciously search for the error line, and sometimes get confused
because I'm looking at the wrong error message.  I'm not sure why it's worse
for compilation buffers than the normal gdb use, but it does seem to be;
maybe it's simply that error message lines are typically much longer and

However, I think maybe the context-lines idea could still work well if the
indication was even more obvious.  It doesn't have to be flashing red, but
perhaps an overlay with, say, a mild grey background color[*] covering the
entire current error message?

I gather than one of the advantages of the new compile mode is that it can
see multiple erorrs on a line, so maybe this would also have the advantage
that it highlights exactly which error is current, rather than just the line.

[*] But if you make a new defface, _don't use a `-face' suffix in the face

The secret to creativity is knowing how to hide your sources.
  --Albert Einstein

reply via email to

[Prev in Thread] Current Thread [Next in Thread]