3 ms·
It should, I originally built it for rspec output but it should work with most common formats that put the line number attached to the path with a colon.
by _chendo_ 7y ago
It should, I originally built it for rspec output but it should work with most common formats that put the line number attached to the path with a colon.
- gnachman 7y agoHey! Glad to see you’re still around. Hope you’re doing well :)
- _chendo_ 7y agoOh hey! Still kicking about but haven't really done Mac dev for a couple of years. Hope you're doing well too and keep up the great work with iTerm2!
- Myrmornis 7y agoOK, but beyond path:line_column there are other common formats in which paths and line numbers are dumped to the terminal, e.g. stack traces. The original idea behind iterm2-dwim was to house a useful collection of regular expressions for capturing these, outside iTerm2, but maybe it would make sense to extend the functionality inside iTerm2? So far iterm2-dwim only implements a handful that I personally needed: Compiler/Linter etc output, e.g. a/b/c.py:18:1: Git diff output (note the initial meaningless "a" or "b"), e.g. a/a/b/c.py Python stack trace, e.g. /a/b/c.py, line 2, in some_function Pdb stack trace, e.g. /a/b/c.py (336)some_function()