Re:Terminal escape sequences in Git commit email field
by arthur2e5 on Monday March 29, 2021 @06:51AM
(#26619838)
With NUL-sepearated output instead of line output people are doing fine. It's unstructured for sure, but how much structure can you put into something as general as grep?
[ Parent
| on HN ]
Re:Terminal escape sequences in Git commit email field
by philsnow on Monday March 29, 2021 @01:06PM
(#26624906)
grep can emit structured GrepResult records that include things like
- the pattern that was searched for
- the search options from the invocation (case, line folding, etc)
- the text of the matched segment
- the byte range of the matched segment within the file
- the line number(s) of the matched segment within the file
- the file name
- contents of any (named) capture groups from the search pattern