From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Why approximate pattern doesn't match?
Date: Tue, 10 May 2016 18:42:30 +0200 [thread overview]
Message-ID: <CAHYJk3R=0yFbi1wE9WmeO6=8NfJTN=t+h4VX9Ym=7uowfdkktA@mail.gmail.com> (raw)
In-Reply-To: <160509205620.ZM17429@torch.brasslantern.com>
On Tue, May 10, 2016 at 5:56 AM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On May 9, 10:11pm, Sebastian Gniazdowski wrote:
> } Subject: Re: Why approximate pattern doesn't match?
> }
> } Hello again,
> } it appears that the approximate matching works only for first word in
> } the *~^* sequence:
> }
> } a=( "git push" )
> } pattern1='git*~^*pash*'
>
> I read that as: git followed by anything, except NOT matching (~)
> anything NOT containing "pash". Who came up with that double-negative?
I think I sent a mail to the list when I discovered it, the operations
simplify to "AND", which we don't have as a primitive. Eg foo~^bar
means result that match both patterns foo and bar. It is most
obviously useful when the second or first pattern is surrounded by *
so that it means *foo*~^*bar* gives files foobazbar, barbazfoo, barfoo
etc.
--
Mikael Magnusson
prev parent reply other threads:[~2016-05-10 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 20:07 Sebastian Gniazdowski
2016-05-09 20:11 ` Sebastian Gniazdowski
2016-05-10 3:56 ` Bart Schaefer
2016-05-10 5:16 ` Sebastian Gniazdowski
2016-05-10 15:05 ` Peter Stephenson
2016-05-10 15:21 ` Sebastian Gniazdowski
2016-05-10 15:40 ` Peter Stephenson
2016-05-10 17:16 ` Sebastian Gniazdowski
2016-05-10 17:29 ` Sebastian Gniazdowski
2016-05-10 18:12 ` Bart Schaefer
2016-05-10 16:42 ` Mikael Magnusson [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='CAHYJk3R=0yFbi1wE9WmeO6=8NfJTN=t+h4VX9Ym=7uowfdkktA@mail.gmail.com' \
--to=mikachu@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).