| Summary: | Enable jump to error for output from external scripts | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Martin Fuhrer <mfuhrer> |
| Component: | Output Views | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | xrigou |
| Priority: | NOR | ||
| Version: | 4.0.80 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Output from External Script | ||
true, I have to investigate how to implement this properly without duplicating code. Hope to get it into 4.2. Are we speaking about the Custom Buildsystem plugin? Because it has the same problem at 4.2+ I hope it gets done soon. In case someone wonders, this bug is still valid. I am retracting all my comments in this bug report. My problem was irrelevant. I am sorry. I think this should work nowadays, please reopen if not. |
Created attachment 51868 [details] Output from External Script Version: 4.0.80 (using KDE 4.4.6) OS: Linux I am using the external script plugin to compile source files using a custom build script provided by my company. I notice that output from the external script is sent to the “Run” tool view. If the script is compiling code and generates compile errors, clicking on the errors in the Run tool view won’t send me to the problematic line in the source code. It would be useful to enable jump to error functionality for this output. Two possible approaches are: * Send external script output to the “Build” tool view, where clicking on errors already jumps to the relevant line of code. * Implement jump to error functionality in the “Run” tool view. Reproducible: Always Steps to Reproduce: 1. Create an external script for compiling code. 2. Click the script to run it on some problematic code files you are editing. 3. Click on a compile error (or warning) in the output in the "Run" tool view. Actual Results: Nothing happens. Expected Results: The file corresponding to the error/warning should be opened, and the cursor placed at the problematic line. Attached image demonstrates my request. When I click on the compile error (HorizonUnitTest.cpp:38 error...) in the "Run" tool view, I would like the file HorizonUnitTest.cpp to open and the cursor to be positioned on line 38. Currently this does not happen.