Re: Feature request: #a (approximate matching) only for spaces

[Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>]

Being skeptical from the beginning, I've just found that fuzzy
matching might not be much better. Doing lsof | fzf and searching for
"listen tcp", gives:

Spotify     459 sgniazdowski   48u    IPv4 0x641c23b7a67dd4e3
0t0       TCP localhost:4371 (LISTEN)

but also tons of other stuff like:

firefox   82115 sgniazdowski  txt      REG                1,1
94656 133710834 /Library/Fonts/DecoTypeNaskh.ttc

where "Library/Fonts/DecoTypeN" is matched. That's even worse than
*a*b*c..., there is no "*l*i*s*t*e*n*t*c*p*" embedded. Guess that what's
important is degree of similarity and showing reasonable matches
first.

Best regards,
Sebastian Gniazdowski


On 8 May 2016 at 08:13, Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx> wrote:
> On 7 December 2015 at 09:22, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>> On Dec 7,  5:44am, Mikael Magnusson wrote:
>> }
>> } % print -l ${~s//(#b)(?)/$match[1]*} # make the pattern g*i*t*p*u*r*g*e*
>>
>> Yeah, but that also matches gfooifootfooifoopfooufoorfoogfooefoo, which
>> I'm not sure is what Sebastian wants.  The pattern
>
> Specifically, it also matches: git pull origin master :) I wonder how
> close one can get with patterns to recently popular fuzzy matching. I
> guess it's not possible, but maybe miracles happen?
>
> Best regards,
> Sebastian Gniazdowski