Version: 3.0b2 (using KDE KDE 3.1.4) Installed from: Compiled From Sources Compiler: gcc-3.x OS: Linux I use linting tools in conjunction with kdevelop. I added a "lint" file menu option. I can right-click on a file, execute my command with the %S option (current filename), and the output is sent to the application view widget. It includes file and line information. Left-clicking on any given line will not take me to the file/line specified in the application view output. I've also tried this with gcc to verify that it was not a problem with the lint output formatting of file and line information. the gcc output exhibits the same (lack of) behavior. It seems like output to the application widget, if it contains file and line information, should open the file at the specified line if the user left clicks on the output line in question.
I concur! This feature is something I've been wanting for quite some time now, but for differents reasons: Basically, when I run the application I'm developping and something goes wrong during runtime (such as a script failing to compile/run), it outputs a message on stdout/stderr with the "file:line: message" format, so I can locate the problem quickly. It would be wonderfull (and I suppose relatively painless to implement) if kdevelop parsed the "Application" output view on mouse clicks just like it does for the "Messages" one!
I have also problems when using Lint. My configuration is slightly different: - KDevelop v3.3.1. - Invoking Lint through special target in makefile. - Lint messages end up in the Messages tab as expected. Unexpected behaviour is that the error messages (Formatted to look like GCC messages) do not lead to the correct line-number in the corresponding source file. However when clicking a few lines lower, the editor window does jump. Example: cd '/data/pledip' && gmake -k -j1 lint-all wine c:\\lint\\lint-nt pledip.lnt *.c PC-lint for C/C++ (NT) Ver. 8.00p, Copyright Gimpel Software 1985-2004 --- Module: bmpio.c --- Module: main.c --- Module: pclopt.c pclopt.c:628: Error 40 Undeclared identifier 'OPT_END2' pclopt.c:628: Error 30 Expected a constant pclopt.c:628: Warning 408 Type mismatch with switch expression pclopt.c:630: Info 788 enum constant 'OPT_END' not used within defaulted switch gmake: *** [lint-all] Error 4 *** Exited with status: 2 *** When clicking the line starting with 'pclopt.c:630:' KDevelop jumps to the correct file but to line 628 instead of 130. The lines above do not cause any jump. When testing larger examples it seems that KDevelop is always at least 4 lines of. So to jump to the location of the error-message on line #1 you have to click on the error message on line #4. This behaviour is only there when the 'Full compiler output' option is selected.
It could be a DOS CR/LF problem. AFAIK we only deal with one (\n).
Hmm, this bug started out as a feature request for the "application" tool view. However, it now seem to have turned into a somewhat unrelated bug report for the "messages" tool view :-) Should I open a new bug for the original wish ? I still very much want the feature described in the first two posts, as does the orignal poster I suppose...
No, don't open a new for the wish. This is still the wish, bugs should be reported separately.
OK. I assume I should had created a new bug for this behaviour. Is this the appropriate step to take now?
*** This bug has been confirmed by popular vote. ***
Anyway, this keeps being a wish, not confirming any bug. What if you capture output into Messages Output window or give choice to do so?
this is basically fixed in kdev4, a plugin providing executing of some other app (like one that executes external tools) can support "doing something" when any entry in the outputview is activated.