dandavison / iterm2-dwim Goto Github PK

E.g. z.py. Would need to ensure that path regexes match a path as simple as that.

Currently a parse rule exists that tries to interpret a relative path as relative to the current directory CWD.

However, it's fairly common to be in an internal directory of the git repo, and yet be looking at a path in some output that is relative to the root of the git repo. In that situation, no parse rule will cerrently match.

We could add a parse rule that works as follows: ask git whether CWD is in a git repo and if so what the root is (git rev-parse --show-toplevel), and try the path relative to that root.

With the current configuration instructions in the README, absolute paths are handled by iTerm2's "Semantic History"

whereas relative paths are handled by the "Paths" regex in "Smart Selection"

However, the default "Paths" regex that comes with iTerm2 does not capture the trailing text, which is where the line number is to be found, if present. E.g. this python traceback will open on line 1, not line 4 as it should:

$ /tmp mkdir z
/tmp cat > z/z.py
a = 1
b = 2
c = 0
a/c
/tmp python z/z.py
Traceback (most recent call last):
  File "z/z.py", line 4, in <module>
    a/c
ZeroDivisionError: integer division or modulo by zero

I think the solution will involve

• Design a suitable regex to use as a "Smart Selection" rule in iTerm2 that passes the appropriate trailing text to iterm2-dwim
• Document how to configure iterm2-dwim in the README.

The default Paths regex that comes with iTerm2 is

\~?/?([[:letter:][:number:]._-]+/+)+[[:letter:][:number:]._-]+/?

So far I've experimented with one variation on this:

Regex:     (\~?/?([[:letter:][:number:]._-]+/+)+[[:letter:][:number:]._-]+/?)([^ ]*)
Parameter: /usr/local/bin/iterm2-dwim \1 \3