Re: Matching a non-match

2021-10-14 Thread Tim Chase
On 2021-10-14 17:34, A. Wik wrote: > Yes, I think so. Is it because \@! is zero-width that it must be > paired with something (eg. ".") that does have width? > > And it matches an empty line because of the \%( ... \)*? Exactly, on both fronts.  -tim -- -- You received this message from

Re: Matching a non-match

2021-10-14 Thread A. Wik
Hi all, On Wed, 13 Oct 2021 at 14:36, Tim Chase wrote: > > On 2021-10-11 23:45, A. Wik wrote: > > > or if you want to match the entire line, you can use: > > > > > > /^\%(\%(exim.input\)\@!.\)*$/ > > > > > > That breaks down to > > > > > > ^ from the start of the line > > > \%(…\)*

Re: Matching a non-match

2021-10-13 Thread Tim Chase
On 2021-10-11 23:45, A. Wik wrote: > > or if you want to match the entire line, you can use: > > > > /^\%(\%(exim.input\)\@!.\)*$/ > > > > That breaks down to > > > > ^ from the start of the line > > \%(…\)*zero or more of these things > >\%(exim.match\)\@! at each of

Re: Matching a non-match

2021-10-11 Thread A. Wik
Thanks to all who replied to my thread! On Sun, 20 Dec 2020 at 17:30, Tim Chase wrote: > > On 2020-12-20 11:09, A. Wik wrote: > > Browsing a directory listing, sometimes I hit lines like these: > > ./spool/exim/input/1FM8sl-4n-Ix-H > > ./spool/exim/input/1FM8sn-4u-OF-D > >

Re: Matching a non-match

2020-12-29 Thread Kenny Stauffer
In a simple test file, this did what I think you're asking: /\v^(.*exim[/]input)@! Notice the use of @! instead of @ Hi all, > > Browsing a directory listing, sometimes I hit lines like these: > ./spool/exim/input/1FM8sl-4n-Ix-H > ./spool/exim/input/1FM8sn-4u-OF-D >

Re: Matching a non-match

2020-12-20 Thread Tim Chase
On 2020-12-20 11:09, A. Wik wrote: > Browsing a directory listing, sometimes I hit lines like these: > ./spool/exim/input/1FM8sl-4n-Ix-H > ./spool/exim/input/1FM8sn-4u-OF-D > ./spool/exim/input/1E9dsQ-4f-MO-D > [... thousands of similar lines ...] > > How can I use "/" to find the

Re: Matching a non-match - workaround: less

2020-12-20 Thread Christian Brabandt
On So, 20 Dez 2020, Sven Guckes wrote: > workaround: > open the file with "less" and right after initiating search with '/' > type '!' and the prompt will switch to "Non-match /". now enter > eg "spool.exim.input" and less will skip all those lines. :-) > that's one of the features i dearly

Re: Matching a non-match - workaround: less

2020-12-20 Thread Tim Chase
On 2020-12-20 14:53, Sven Guckes wrote: > workaround: > open the file with "less" and right after initiating search with '/' > type '!' and the prompt will switch to "Non-match /". now enter > eg "spool.exim.input" and less will skip all those lines. :-) > that's one of the features i dearly miss

Re: Matching a non-match

2020-12-20 Thread Charles Campbell
A. Wik wrote: Hi all, Browsing a directory listing, sometimes I hit lines like these: ./spool/exim/input/1FM8sl-4n-Ix-H ./spool/exim/input/1FM8sn-4u-OF-D ./spool/exim/input/1E9dsQ-4f-MO-D [... thousands of similar lines ...] How can I use "/" to find the next line not matching the

Re: Matching a non-match - workaround: less

2020-12-20 Thread Sven Guckes
* A. Wik [2020-12-20 14:39]: > Browsing a directory listing, sometimes I hit lines like these: > ./spool/exim/input/1FM8sl-4n-Ix-H > ./spool/exim/input/1FM8sn-4u-OF-D > ./spool/exim/input/1E9dsQ-4f-MO-D > [... thousands of similar lines ...] > > How can I use "/" to find the next

Matching a non-match

2020-12-20 Thread A. Wik
Hi all, Browsing a directory listing, sometimes I hit lines like these: ./spool/exim/input/1FM8sl-4n-Ix-H ./spool/exim/input/1FM8sn-4u-OF-D ./spool/exim/input/1E9dsQ-4f-MO-D [... thousands of similar lines ...] How can I use "/" to find the next line not matching the above pattern?