https://bugs.kde.org/show_bug.cgi?id=501004
Bug ID: 501004 Summary: custom command for file paths does not correctly parse COLUMN for Node.js stack traces Classification: Applications Product: konsole Version: 23.08.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: spam10...@gmail.com Target Milestone: --- SUMMARY I'm on Ubuntu and cannot easily test the latest version of Konsole, but I did have a look at the code (github dot com/KDE/konsole/blob/dc93ba3fa5c262509058b817d72cd9d89266920d/src/filterHotSpots/FileFilterHotspot.cpp#L82) and it appears that this is still what I'd consider to be a bug, or perhaps a feature request? Konsole will not parse file paths in this form: some/file.js:LINE:COLUMN This is the format that Node.js spews stack traces, making web dev a bit tedious when using Konsole. Instead, this verison of Konsole supports: some/file.cpp:LINE:COLUMN: // note trailing colon The code handling this is here: github.com/KDE/konsole/blob/dc93ba3fa5c262509058b817d72cd9d89266920d/src/filterHotSpots/FileFilterHotspot.cpp#L82 There's a thread with all repro steps and further detail here: https://discuss.kde.org/t/konsole-click-to-open-file-uses-default-rather-than-custom-text-editor-command/29848/2 Thank you. -- You are receiving this mail because: You are watching all bug changes.