grep line number output w/ -[A-C] doesn't trigger Semantic History
Thanks for filing an issue! Please answer the questions below so I can help you.
- iTerm2 version: Build 3.2.9
- OS version:
sw_vers
ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G7024
Detailed steps to reproduce the problem:
grep -Hn -C 1 line <( echo -e 'non-match\nnon-match\nleft-flush line\n not flush line\nnon-match\nnon-match' ) <( echo 'non-match\nnon-match\nboop line\nnon-match\nnon-match' )
/dev/fd/11-2-non-match
/dev/fd/11:3:left-flush line
/dev/fd/11:4: not flush line
/dev/fd/11-5-non-match
--
--
/dev/fd/12-2-non-match
/dev/fd/12:3:boop line
/dev/fd/12-4-non-match
grep -Hn -B 1 line <( echo -e 'non-match\nnon-match\nleft-flush line\n not flush line\nnon-match\nnon-match' ) <( echo 'non-match\nnon-match\nboop line\nnon-match\nnon-match' )
/dev/fd/11-2-non-match
/dev/fd/11:3:left-flush line
/dev/fd/11:4: not flush line
--
/dev/fd/12-2-non-match
/dev/fd/12:3:boop line
grep -Hn -A 1 line <( echo -e 'non-match\nnon-match\nleft-flush line\n not flush line\nnon-match\nnon-match' ) <( echo 'non-match\nnon-match\nboop line\nnon-match\nnon-match' )
/dev/fd/11:3:left-flush line
/dev/fd/11:4: not flush line
/dev/fd/11-5-non-match
--
/dev/fd/12:3:boop line
/dev/fd/12-4-non-match
What happened:
Resulting non-matched lines (those displayed as a result of using -A
, -B
, or -C
don't conform to Semantic History's rules and can't be clicked to open the associated file.
What should have happened: Both file paths featuring colons and dashes as line number delimiters should be clickable.