zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Why approximate pattern doesn't match?
Date: Mon, 9 May 2016 20:56:20 -0700	[thread overview]
Message-ID: <160509205620.ZM17429@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVBxQCb_-2pKSKqGbmw0xMcz20vJvQfVwa2RQYV3C2twzA@mail.gmail.com>

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?

} Any solution?

It doesn't seem so.

	/*
	 * By default, approximations are turned off in exclusions:
	 * we need to do this here as otherwise the code compiling
	 * the exclusion doesn't know if the flags have really
	 * changed if the error count gets restored.
	 */

So you don't get approximate non-matching, only approximate matching.

You can possibly refactor it this way:

    a=( "git push" )
    pat1='git*'
    pat2='*pash*'
    echo ${(@M)${(@M)a:#(#ia2)$~pat1}:#(#ia2)$~pat2}


  reply	other threads:[~2016-05-10  3:55 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 [this message]
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

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=160509205620.ZM17429@torch.brasslantern.com \
    --to=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).