Summary: | Direct click on file in grep result doesn't open file | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | maciej.stanczew, piotr.mierzwinski |
Priority: | NOR | ||
Version: | 20.12.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | konsole - bash_profile - mouse |
Description
Piotr Mierzwinski
2021-01-21 20:47:23 UTC
Created attachment 135040 [details]
konsole - bash_profile - mouse
I think this is related with: https://invent.kde.org/utilities/konsole/-/merge_requests/224 This now (mostly) works for me with Konsole 21.12.0, Frameworks 5.89.0, and Plasma 5.23.5. I can ctrl-click results of grep -n, like: test.txt:5: match and the file test.txt is opened in Kate at line 5, just as expected. This also works for paths which include subdirectories (previously those were not even clickable): dir/test.txt /tmp/dir/test.txt dir/test.txt:5: match /tmp/dir/test.txt:5: match It doesn't however work reliably if the line which matches doesn't start with a whitespace. For example, if I grep for "match" and the line is: test.txt:5:match-n then ctrl-click will work; however if there is a digit in the output: test.txt:5:match-1 then I get "The file or folder /tmp/dir/test.txt:5:match-1 does not exist". It seems to be a problem only for digits, all other printable ASCII characters are fine. |