Implement navigable test output for Go runner #32
Description
This feature enhances the Chase buffer by making test and compilation errors "clickable," allowing users to jump directly from a failure log to
the corresponding source code line.
Current Workflow Issues:
When a Go test fails, users must manually read the filename and line number from the Chase buffer and then search for/open the file to fix the
issue. This creates friction and slows down the TDD cycle.
Proposed Solution:
- Implement a buffer-local keymap () within the Chase results buffer.
- Create a Lua handler that captures the current line text under the cursor.
- Use pattern matching (Regex) to extract the filename and line number from common Go error formats (e.g., file.go:line:col or file.go:line).
- Implement the jump logic to open the target file in the previous window and position the cursor on the reported line.
Scope:
Initial implementation focused on Go runner patterns, designed to be extensible for other languages in the future.