It would raise some questions. Eg. grep -vc apple input.txt counts the number of lines not containing "apple". If we extend this functionality for multiline patterns, what should mgrep -vc 'apple.*$^.*plum' input.txt give back? This is not really definite, since the number of non-matching multiline blocks is the number of many different-length blocks...
Maybe it is meaningful if disabled in conjunction with -c but I would still need to think over its interaction with the other options.
What would you like to use this option for exactly? To filter out multiline blocks from an input? Eg. mgrep -v 'apple.*$^.*plum' input.txt to get rid of all two-line blocks having "apple" in the first line and "plum" in the second?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would raise some questions. Eg.
grep -vc apple input.txtcounts the number of lines not containing "apple". If we extend this functionality for multiline patterns, what shouldmgrep -vc 'apple.*$^.*plum' input.txtgive back? This is not really definite, since the number of non-matching multiline blocks is the number of many different-length blocks...Maybe it is meaningful if disabled in conjunction with
-cbut I would still need to think over its interaction with the other options.What would you like to use this option for exactly? To filter out multiline blocks from an input? Eg.
mgrep -v 'apple.*$^.*plum' input.txtto get rid of all two-line blocks having "apple" in the first line and "plum" in the second?Implemented in v1.1.1.
-v is not allowed together with -c. All else should be possible.