zsh-users
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@macports.org>
To: TJ Luoma <luomat@gmail.com>
Cc: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: input foo, output '[F|f][O|o][O|o]'?
Date: Mon, 1 Jul 2013 21:30:22 -0400	[thread overview]
Message-ID: <FFE8CEBD-EE41-4104-B4BF-DED31ED99598@macports.org> (raw)
In-Reply-To: <E7CF18D5-CB4B-4E80-B7E0-40D5930E42DD@gmail.com>

On Jul 1, 2013, at 8:58 PM, TJ Luoma <luomat@gmail.com> wrote:

> On 1 Jul 2013, at 14:44, ZyX wrote:
> 
>> By the way, what regex engine is your output for? Any I am aware of parse "[N|n]" as "either one of three characters: N, n, or pipe".
> 
> Really? I can think of several that support it. Maybe it's because I'm old enough to remember when a lot of these utilities didn't have 'ignore case'
> 
> % echo "foo\nbar\nbat" | egrep -v '[F|f]'
> bar
> bat
> 
> % echo "foo\nbar\nbat" | sed 's#[F|f][O|o][O|o]#XXX#g'
> XXX
> bar
> bat

These regex are not matching what you think they are matching. For sure, "[F|f]" matches both lowercase and uppercase F, but as ZyX said, it also matches pipe characters:

    % echo "foo\nbar\nbaz\nbar|||baz" | egrep -v '[F|f]'
    bar
    baz

    % echo "foo\nbar\nbaz\nbar|||baz" | sed 's/[F|f][O|o][O|o]/XXX/g'
    XXX
    bar
    baz
    barXXXbaz

You are probably thinking of "(F|f)"; you should just use "[Ff]".

> You can also use it for matching case/esac :
> 
> case "$i" in
> 	[C|c][R|r][A|a][S|s][H|h][P|p][L|l][A|a][N|n])
> 			echo "matched crashplan"
> 	;;
> 
> 	*)
> 			echo "No Match"
> 	;;
> 
> esac

Same misconception here; pipes in patterns' bracket expressions have no special meaning. You can remove all the pipes from your example, and it would still work.

    % case "crasHPLan" in
    case>           [Cc][Rr][Aa][Ss][Hh][Pp][Ll][Aa][Nn]) echo "matched";;
    case>           *) echo "did not match";;
    case> esac
    matched

vq

  reply	other threads:[~2013-07-02  1:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 17:59 TJ Luoma
2013-07-01 18:44 ` ZyX
2013-07-02  0:58   ` TJ Luoma
2013-07-02  1:30     ` Lawrence Velázquez [this message]
2013-07-02  1:53     ` Benjamin R. Haskell
2013-07-02  4:24       ` TJ Luoma
2013-07-02  3:51     ` ZyX
2013-07-02  4:00       ` ZyX
2013-07-02 23:24         ` Phil Pennock
2013-07-01 19:37 ` Phil Pennock
2013-07-02  0:24   ` TJ Luoma
2013-07-01 23:51 ` Alex Satrapa
2013-07-02  0:38   ` Kurtis Rader
2013-07-02  1:11     ` TJ Luoma

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=FFE8CEBD-EE41-4104-B4BF-DED31ED99598@macports.org \
    --to=larryv@macports.org \
    --cc=luomat@gmail.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).