From: Wayne Davison <wayned@users.sourceforge.net>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: PATCH: fixing ${1+"$@"} when word-splitting
Date: Mon, 13 Feb 2006 11:48:42 -0800 [thread overview]
Message-ID: <20060213194842.GF6952@dot.blorf.net> (raw)
In-Reply-To: <20060213174338.GC6952@dot.blorf.net>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
On Mon, Feb 13, 2006 at 09:43:38AM -0800, Wayne Davison wrote:
> insertlinknode(&foo, n, (void *)x), incnode(n);
> + mult_isarr = 1;
> }
This turned out to be inadequate in the face of the following expansion:
print -l ${=1:-$LINES $COLUMNS}
This is because mult_isarr got reset to 0. The attached patch fixes
this (which should be applied to whatever patched version you're using).
..wayne..
[-- Attachment #2: better-splitting.diff --]
[-- Type: text/plain, Size: 774 bytes --]
--- Src/subst.c 2006-02-13 11:35:16.000000000 -0800
+++ Src/subst.c 2006-02-13 11:40:48.000000000 -0800
@@ -337,6 +337,7 @@
if (split) {
LinkNode n = firstnode(&foo);
int inq = 0, inp = 0;
+ split = 0; /* used to flag if we really split anything */
for ( ; *x; x += l+1) {
char c = (l = *x == Meta) ? x[1] ^ 32 : *x;
if (!inq && !inp && isep(c)) {
@@ -349,7 +350,7 @@
if (!*x)
break;
insertlinknode(&foo, n, (void *)x), incnode(n);
- mult_isarr = 1;
+ split = 1;
}
switch (c) {
case Dnull:
@@ -375,6 +376,9 @@
mult_isarr = omi;
return 0;
}
+ if (split)
+ mult_isarr = 1;
+
if ((l = countlinknodes(&foo)) > 1 || (a && mult_isarr)) {
p = r = hcalloc((l + 1) * sizeof(char*));
while (nonempty(&foo))
next prev parent reply other threads:[~2006-02-13 19:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 23:32 Libtool/zsh quoting problem David Gómez
2006-02-10 8:46 ` DervishD
2006-02-10 9:48 ` David Gómez
2006-02-10 11:34 ` DervishD
2006-02-10 12:56 ` David Gómez
2006-02-10 14:25 ` DervishD
2006-02-10 18:27 ` David Gómez
2006-02-10 19:31 ` DervishD
2006-02-11 9:36 ` [SOLVED] Libtool/zsh quoting problem: a zsh... bug? DervishD
2006-02-11 10:21 ` Andrey Borzenkov
2006-02-11 11:06 ` DervishD
2006-02-11 11:33 ` David Gómez
2006-02-11 12:06 ` DervishD
2006-02-11 12:28 ` Andrey Borzenkov
2006-02-11 18:07 ` DervishD
2006-02-11 12:21 ` DervishD
2006-02-11 18:14 ` Wayne Davison
2006-02-11 18:22 ` DervishD
2006-02-11 18:58 ` Wayne Davison
2006-02-11 19:42 ` Bart Schaefer
2006-02-12 4:50 ` Wayne Davison
2006-02-12 20:28 ` Peter Stephenson
2006-02-13 10:56 ` Peter Stephenson
2006-02-12 7:46 ` Andrey Borzenkov
2006-02-12 7:54 ` Andrey Borzenkov
2006-02-12 20:26 ` Peter Stephenson
2006-02-13 10:53 ` PATCH: fixing ${1+"$@"} when word-splitting Wayne Davison
2006-02-13 11:34 ` Peter Stephenson
2006-02-13 17:43 ` Wayne Davison
2006-02-13 18:08 ` Peter Stephenson
2006-02-13 19:00 ` Wayne Davison
2006-02-13 19:33 ` Wayne Davison
2006-02-13 19:33 ` Peter Stephenson
2006-02-13 20:11 ` Wayne Davison
2006-02-13 19:48 ` Wayne Davison [this message]
2006-02-13 11:40 ` DervishD
2006-02-14 7:14 ` Wayne Davison
2006-02-15 10:31 ` Wayne Davison
2006-02-15 11:35 ` Wayne Davison
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=20060213194842.GF6952@dot.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=pws@csr.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).