| Summary: | highlight recent console display | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Daniel Herring <dherring> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED LATER | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Hi,
That's a good idea.
I find the easiest way of parsing 'make' output is to use Vim's error list which saves the hassle of trying to search it manually. It can be used even when you are doing the editing in a different text editor.
1. Start Vim ("vim") and type ":make" and press Enter to execute the 'make' command in the current location
2. When the output stops, either when make finishes or if you press <Control>+C, you will be taken back to Vim which will take you to the first warning or error message ouput by the compiler. For simple projects this works well.
3. To browse the errors from the last make, type ":cope" and press Enter to open the error window, and you can browse it using the Up/Down arrow keys
4. To jump quickly to the first fatal error that causes the compilation to fail, type "/err" and press Enter (which almost always works since the guilty line will begin with the text "error:"
Steps 1 and 3,4 can be bound to a handy shortcut key combination (I use the function keys) to make the process even quicker.
I hope to have some facilities for highlighting lines of text matching particular expressions in KDE 4. This should help here. I'll close this for now - if anyone wants to code this reopen this. |
Version: (using KDE KDE 3.5.4) Installed from: Unspecified When developing code, a common console usage pattern is while(compile-time bugs) { `make` decipher messages to fix errors } The problem is that the `make` line is small when compared to the multi-page error reports that can spew out, and most bugs are best identified in the first few lines of output. Thus, I would like to have konsole change the background color for all text output since the last user input, and use another color to highlight output between the two previous user inputs (e.g. `make` and <Control>-C). This highlighting should then disappear as new commands are typed in. In this way, a strong visual cue would indicate which output is "current". Just coloring the prompt is insufficient (easily done now) -- its hard to distinguish one prompt from another after scrolling several pages. I think a feature like this would be useful for non-compiling tasks (such as listing or grepping) as well.