Re: add INVERT to re-search-{forward, backward}

[Lennart Borgman (gmail)]

Juri Linkov wrote:
>>> Instead of this, I think the change should be done at the occur level,
>>> since occur's algorithm is line-based and can skip lines that contain
>>> a given regexp.  This could be similar to the algorithm used by the
>>> command `flush-lines' in the same file.  `occur' currently works like the
>>> command `keep-lines' that keeps lines containing the specified regexp.
>>> But with a new INVERT argument, `occur' could work like `flush-lines' that
>>> keep everything except lines containing the specified regexp.
>> This is also similar to grep etc.
> 
> Yes, as a line-oriented tool, grep's -v --invert-match option is what
> could be modelled in occur.
> 
> Then a negative prefix argument of `occur' could mean inverting the
> regexp and displaying non-matching lines.

Maybe it also would be practical to be able to access that function from
within the occur window too?