| Syntax highlighting of build log? [message #118847] |
Thu, 02 September 2004 05:50  |
Eclipse User |
|
|
|
Because many C++ error messages are pretty long and tend to flow over many
lines, the Problems view usually isn't much help, as it only catches the
first line of any message. Added to that, by default the Problems view
seems to sort the error messages by severity, folder, resource and then
location. Normally I find that when looking at a build log, the first
compile error of a sequence is the interesting one, the rest are "fall
out". For these reasons I don't tend to use the Problems view.
Instead I look at the build console directly, but what would be nice would
be if it where syntax highlighted a bit, and more importantly that the
code locations where hypertext linked to the relevant place in the code.
The build log is being analysed for exactly this information anyway in
order to populate the Problems view. My recollection is that Emacs did
this very well (though I'm going back a few years).
|
|
|
| Re: Syntax highlighting of build log? [message #120242 is a reply to message #118847] |
Wed, 08 September 2004 21:11  |
| Eclipse User |
|
|
|
Feel free to raise a feature request @ bugs.eclipse.org.
JC
"Tom Quarendon" <tomq@teamwpc.co.uk> wrote in message
news:ch6qd4$be$1@eclipse.org...
> Because many C++ error messages are pretty long and tend to flow over many
> lines, the Problems view usually isn't much help, as it only catches the
> first line of any message. Added to that, by default the Problems view
> seems to sort the error messages by severity, folder, resource and then
> location. Normally I find that when looking at a build log, the first
> compile error of a sequence is the interesting one, the rest are "fall
> out". For these reasons I don't tend to use the Problems view.
>
> Instead I look at the build console directly, but what would be nice would
> be if it where syntax highlighted a bit, and more importantly that the
> code locations where hypertext linked to the relevant place in the code.
> The build log is being analysed for exactly this information anyway in
> order to populate the Problems view. My recollection is that Emacs did
> this very well (though I'm going back a few years).
>
|
|
|
Powered by
FUDForum. Page generated in 0.05748 seconds
Home