Issue #19451 has been updated by schneems (Richard Schneeman). It's also worth mentioning that not all syntax errors have an associated path. `eval`, code piped to STDIN, and `ruby -e` can have invalid syntax but might not have an associated path. In the discussion around adding SyntaxSuggest to Ruby 3.2 I asked for something like `SyntaxError#source` that would let me access the source code for these elements, but it was not implemented before 3.2 was released. ---------------------------------------- Feature #19451: Extract path and line number from SyntaxError? https://bugs.ruby-lang.org/issues/19451#change-101960 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- There doesn't seem to be any official way to extract the path and line number from a syntax error. There are two ways I can see us dong this: - Provide explicit `path` and `line_number` attributes. - Prepend them to `backtrace_locations`. The nice thing about the latter approach is that it will just work with existing tools which understand how to highlight code based on backtrace locations. Maybe we should do both? -- https://bugs.ruby-lang.org/