Issue #21960 has been updated by Eregon (Benoit Daloze). There is also a good point that what follows a second `:` should be the column and not `in`, that's standard in many tools, including `gcc` and `clang` which look like: ``` $ echo 'int main() {' > foo.c $ gcc a.c a.c: In function ‘main’: a.c:1:1: error: expected declaration or statement at end of input 1 | int main() { | ^~~ $ clang a.c a.c:1:13: error: expected '}' 1 | int main() { | ^ a.c:1:12: note: to match this '{' 1 | int main() { | ^ 1 error generated. ``` Since Ruby doesn't show the column, there should be no second `:`. (FWIW gcc/clang have a third `:` but at least there is a space after) ---------------------------------------- Feature #21960: Improve #backtrace to not confuse terminals https://bugs.ruby-lang.org/issues/21960#change-116810 * Author: svoop (Sven Schwyn) * Status: Open ---------------------------------------- The `#backtrace` of exceptions are currently printed like so: ``` /path/to/whatever.rb:8:in `/' /path/to/whatever.rb:8:in `show' (...) ``` Most terminals recognize `/path/to/whatever.rb:8` as a local file and make it clickable as "open in editor", however, some (e.g. Ghostty) include everything up to the next whitespace, in this case `/path/to/whatever.rb:8:in`. This is then used as an argument to `open` (on macOS) which will not work due to the `:in` part. There are two ways to improve this: ## Replace the colon with a space Given the existence of `#backtrace_locations` which is better suited for programmatically working with backtrace locations, it should not break things to slightly modify the `#backtrace` to look like this: ``` /path/to/whatever.rb:8 in `/' /path/to/whatever.rb:8 in `show' (...) ^^^ space instead of colon ``` ## Add OCS 8 sequences [OCS 8](https://github.com/Alhadis/OSC8-Adoption) are the `<a>` tag for terminal output. While many terminals support it, it might cause visual noise in logs and therefore would have to be an opt-in feature e.g. via a Ruby interpreter argument. -- https://bugs.ruby-lang.org/