From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: [SOLVED] Libtool/zsh quoting problem: a zsh... bug?
Date: Sat, 11 Feb 2006 19:42:53 +0000 [thread overview]
Message-ID: <1060211194253.ZM6064@candle.brasslantern.com> (raw)
In-Reply-To: <20060211181440.GA30984@dot.blorf.net>
On Feb 11, 10:14am, Wayne Davison wrote:
}
} + if (spbreak && (*s == Dnull || *s == Snull))
} + spbreak = 0;
}
} This will turn off word-splitting if the string started with a single or
} a double quote. This is incomplete because the arg may be something
} more complicated (such as: 'one' 'two' 'three four'), but it seems
} better than what we have now.
I experimented with but rejected a similar patch back around the time
of the previous discussion because of what happens with ${1+word "$@"}.
It seemed better to me for the shell to behave consistently even if not
posixly-correctly, and I'm loathe to mask an obvious bug with a less-
obvious one.
However, I wouldn't object to Wayne's patch if others think it's a good
idea.
} One question I have is what to do about ${=1:"$@"}? In the patch above,
} I chose to let the double quotes override the '='. If that is not
} desired, change the new "if" to only trigger disallow an spbreak of 2:
I think the latter would be more consistent with other treatment of
${=...}, but again it's not a big deal.
--
Bart Schaefer
http://www.well.com/user/barts
next prev parent reply other threads:[~2006-02-11 19:43 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 [this message]
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
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=1060211194253.ZM6064@candle.brasslantern.com \
--to=schaefer@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).