zsh-users
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: difference between ~ & ^ negation
Date: Fri, 3 Jan 2014 02:55:06 +0100	[thread overview]
Message-ID: <CAHYJk3Sk=AorY+rX6yNC+DNXnrH_9Z=PTjsO=irPrv3rg9KrTA@mail.gmail.com> (raw)
In-Reply-To: <140102133636.ZM10014@torch.brasslantern.com>

On 2 January 2014 22:36, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 2,  9:01pm, Peter Stephenson wrote:
> } Subject: Re: difference between ~ & ^ negation
> }
> } On Wed, 01 Jan 2014 13:44:59 -0800
> } Bart Schaefer <schaefer@brasslantern.com> wrote:
> } > Important note: ^ is special only in cases where / is special (globs).
> }
> } That's not true...
> }
> } setopt extendedglob
> } [[ foo = ^foo ]] || print foo actually is foo
> } [[ bar = ^foo ]] && print but bar is not foo
> }
> } "^" is still special here; the difference is that if a "/" appeared
> } after it *that* wouldn't be special in this context
>
> Hmm.  So what does that mean about a "^" appearing after a "^" ?  That
> is, since / is not special, the expression ^foo/^bar means something
> completely different in pattern context and file generation context?
>
> That second caret is the usage I was referring to when I said "only in
> cases where / is special".  (Whether or not there is a leading caret.)
>

I think of ^foo as a * that won't match "foo", so you can have
foo/bar^baz and it would match bar* but not barbaz, and if you think
of it like that it's not really that confusing. ^foo/^bar is then just
*/* that won't match */bar or foo/*.

-- 
Mikael Magnusson


  parent reply	other threads:[~2014-01-03  1:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 15:28 zzapper
2014-01-01 21:44 ` Bart Schaefer
2014-01-02 21:01   ` Peter Stephenson
2014-01-02 21:36     ` Bart Schaefer
2014-01-02 22:14       ` Peter Stephenson
2014-01-03  1:55       ` Mikael Magnusson [this message]
2014-01-03  7:37         ` Bart Schaefer
2014-01-03 19:48           ` Peter Stephenson
2014-01-03 20:10             ` Peter Stephenson
2014-01-03 21:43               ` Bart Schaefer
2014-01-04 21:11                 ` zzapper
2014-01-05 10:01                   ` Eike von Seggern
     [not found] ` <8lp61n01B02mHnv01lp8uc>
2014-01-03 20:56   ` how to shut off auto spell steve
2014-01-03 21:52     ` Bart Schaefer
     [not found]     ` <9ZwH1n01Z02mHnv01ZwLWZ>
2014-01-03 22:07       ` steve

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='CAHYJk3Sk=AorY+rX6yNC+DNXnrH_9Z=PTjsO=irPrv3rg9KrTA@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).