Bug 502077

Summary: File parsing does not correctly opens files from rustc output
Product: [Applications] konsole Reporter: Hugues Morisset <morisset.hugues>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED DUPLICATE    
Severity: minor CC: christoph
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: All   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Hugues Morisset 2025-03-27 15:57:19 UTC
SUMMARY

On opening file that fails to compile with rustc using the mouse, konsole tries to opens a non existing file when :LINE:COLUMN is specified.

STEPS TO REPRODUCE
1. touch /tmp/aa
2. echo /tmp/aa:10:2
3. Press Alt + click on the output

OBSERVED RESULT

> The file or folder /tmp/aa:10 does not exist.

EXPECTED RESULT

File opening at the right line and column

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.2
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION

[The code](https://github.com/KDE/konsole/blob/master/src/filterHotSpots/FileFilterHotspot.cpp#L80) expect the line to end with ':' (3 ':' in total)

rustc output looks like this:

```
error[E0277]: the trait bound `Untyped: CompatibleType<AdditionalValueList, Pg>` is not satisfied
   --> src/additional_values.rs:35:32
    |
35  |         .load::<AdditionalValueList>(&mut conn)
    |          ----                        ^^^^^^^^^ the trait `CompatibleType<AdditionalValueList, Pg>` is not implemented for `Untyped`
    |          |
    |          required by a bound introduced by this call
    |
    = help: the trait `CompatibleType<U, DB>` is implemented for `Untyped`
```

maybe the regexp could be modified to accept both a ':' and '\n' ?
Comment 1 Christoph Cullmann 2025-03-30 16:14:40 UTC
https://invent.kde.org/utilities/konsole/-/merge_requests/1086

can you test that patch?
Comment 2 Christoph Cullmann 2025-03-30 16:14:53 UTC

*** This bug has been marked as a duplicate of bug 1004 ***
Comment 3 Christoph Cullmann 2025-03-30 16:15:02 UTC

*** This bug has been marked as a duplicate of bug 501004 ***