[Bug 19688] autoscroll to the first error/warning

Maciej Pilichowski bluedzins at wp.pl
Wed Jul 2 12:55:37 UTC 2008

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
bluedzins wp pl changed:

           What    |Removed                     |Added
                 CC|                            |apaku gmx de

------- Additional Comments From bluedzins wp pl  2008-07-02 14:55 -------
> I don't see it valuable enough to just scroll to an error. If there's an
> error you almost always want to fix it, so jumping to the place is exactly
> what you want. I don't see enough benefit for a relatively complicated
> support for just scrolling to an error item. 

Because often the error pointed out by compiler is not the error place.

File A:

10 files which include file A, and file B (11th on the list):

Something S;
s.x = 5;

And then you do some changes + you make typo in A;

The error will be B file.

This very _rough_ example, but I see it all the time, that it would be useful for me to see error first and then decide if I want to jump to it, or not.

Andreas, besides -- what harms is done by skipping lines with info about compiled files?

More information about the KDevelop-devel mailing list