iTerm2 Supply PWD to coprocess in capture output trigger
Confirm - I guess that's a bug in iTerm2.
IMHO, the sub-shell in which your command is executed should point to the same working directory as your main shell (at that point). It doesn't, and it actually happens to be / - which is bad, and prevents your script/any editor from finding the file.
Just as a side note in case someone is using &quot;capture output&quot; in combination with clang or clang++: there is an ugly workaround... one can force the compiler to print absolute paths only, even if the inputs were given as relative paths:
`-fdiagnostics-absolute-paths`