From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Feature request: #a (approximate matching) only for spaces
Date: Sun, 8 May 2016 08:23:00 +0200 [thread overview]
Message-ID: <CAKc7PVB4s64ctRWBky7kSk+ME9Pnkf90OcmbkB=NGg5j1FziVw@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDrWYKAS-0x1Qfc3+Rkhc6m98-Hdm7-zNDZ9BfQduBFHQ@mail.gmail.com>
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@gmail.com> wrote:
> On 7 December 2015 at 09:22, Bart Schaefer <schaefer@brasslantern.com> 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
prev parent reply other threads:[~2016-05-08 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 8:43 Sebastian Gniazdowski
2015-12-07 4:44 ` Mikael Magnusson
2015-12-07 8:22 ` Bart Schaefer
2016-02-19 6:21 ` Sebastian Gniazdowski
2016-02-19 19:13 ` Bart Schaefer
2016-02-20 19:16 ` Bart Schaefer
2016-02-20 19:19 ` Bart Schaefer
2016-05-08 6:13 ` Sebastian Gniazdowski
2016-05-08 6:23 ` Sebastian Gniazdowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKc7PVB4s64ctRWBky7kSk+ME9Pnkf90OcmbkB=NGg5j1FziVw@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).