From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: <zsh-workers@sunsite.dk>
Subject: Re: Patterns quoting in subscript (was: Re: PATCH: Assorted parameter stuff)
Date: Wed, 18 Apr 2001 17:26:22 +0000 [thread overview]
Message-ID: <1010418172622.ZM30038@candle.brasslantern.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0104181227270.29688-100000@itsrm2.mow.siemens.ru>
In-Reply-To: <Pine.SV4.4.33.0104181243140.2545-100000@itsrm2.mow.siemens.ru>
On Apr 18, 12:34pm, Andrej Borsenkow wrote:
} Subject: Re: Patterns quoting in subscript (was: Re: PATCH: Assorted param
}
} On Wed, 18 Apr 2001, Bart Schaefer wrote:
} >
} > schaefer[507] print -r $foo[(r)\\\\\?]
} > \?
} >
} > The reason you need five is that [...] is parsed as if double quoted,
} > except that \] is magic instead of \". Then the pattern inside it is
} > tokenized by (r) before being passed to patcompile(). So it goes like:
} >
} > parse tokenize pattern
} > \\ \\ \? --> \\ \? --> \?
} >
} > (In double quotes, \\ --> \ but \? --> \?.)
}
} O.K., any chance to explain the above in Zsh doc?
Yes, I just don't want to spend time writing doc if this change is going
to cause some other problem and therefore not be included.
} Just to make sure that I understand:
}
} - "as if in double quotes" means, that I cannot use "..." or '...' quoting
} inside of subscript, only back-slash is possible?
It's exactly like quoting for $[...] math expressions, except that (as
of 14008) spaces are not permitted. Which for a traditional numeric
subscript makes sense, as it *is* a math expression.
} - the rule for ``\\'' and ``\$'' still aplies? But ``\"'' is parsed as
} *two* characters?
Yes.
On Apr 18, 12:45pm, Andrej Borsenkow wrote:
}
} O.K., but why when I add additional backslashes I still get a match?:
}
} bor@itsrm2:~%> print -r $foo[(r)\\\\\\\\\?]
} \?
}
} ?? It seems to happen for any number of extra backslashes.
Well, sigh, patcompile() also apparently does a level of backslash-removal,
so i've forgotten one step in the explanation above. It's something like:
parse tokenize pattern match
\\ \\ \? --> \\ \? --> \? --> \?
\\ \\ \\ \\ \? --> \\ \\ \? --> \\ ? --> \?
Then you also have to remember that `?' as a metacharacter matches any
character, so one extra backslash will result in a pattern that matches
by wildcard rather than by a literal question-mark. So if you want to
match 4 backslashes, you need 16 backslashes; but if you want to match
4 backslashes followed by a literal question mark, you need a whopping
34 backslashes, because you have to double all 16 of those backslashes
and then add two more to quote the `?' itself.
Clearly this is silly; it results because of the extra call to parsestr()
that happens when the `needtok' loop in getarg() detects an ispecial()
(the `?' in this example). I'll see if that can't be made to behave a
bit more intelligibly.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-04-18 17:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 8:06 PATCH: Assorted parameter stuff Bart Schaefer
2001-04-17 3:54 ` Example from manual seems broken F. G. Marx
2001-04-17 4:45 ` Bart Schaefer
2001-04-18 6:57 ` PATCH: Assorted parameter stuff Bart Schaefer
2001-04-18 8:44 ` Sven Wischnowsky
2001-04-19 3:57 ` Bart Schaefer
2001-04-19 7:05 ` Sven Wischnowsky
2001-04-19 8:53 ` fpath problem on clean install Andrej Borsenkow
2001-04-19 9:50 ` PATCH: " Sven Wischnowsky
2001-04-19 14:02 ` Andrej Borsenkow
2001-04-19 9:20 ` PATCH: Assorted parameter stuff Andrej Borsenkow
2001-04-19 9:47 ` Bart Schaefer
2001-04-19 9:34 ` Bart Schaefer
2001-04-20 5:20 ` Bart Schaefer
2001-04-17 18:30 ` Patterns quoting in subscript (was: Re: PATCH: Assorted parameter stuff) Andrej Borsenkow
2001-04-18 7:38 ` Bart Schaefer
2001-04-18 8:10 ` Bart Schaefer
2001-04-18 8:34 ` Andrej Borsenkow
2001-04-18 8:45 ` Andrej Borsenkow
2001-04-18 17:26 ` Bart Schaefer [this message]
2001-04-18 20:14 ` Bart Schaefer
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=1010418172622.ZM30038@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).