From: John Lumby <johnlumby@hotmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: <zsh-workers@zsh.org>, autoconf maillist <autoconf@gnu.org>
Subject: RE: Fix testsuite errors due to shell quoted parameter expansion issue.
Date: Wed, 4 Aug 2010 13:06:48 -0400 [thread overview]
Message-ID: <COL116-W22D62FDC242BA2072A0328A3AF0@phx.gbl> (raw)
In-Reply-To: <4C5986DC.1080809@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Eric Blake wrote> On 08/04/2010 09:18 AM, John Lumby wrote:
>
> >
> > Re the statement
> >
> > since "$e" is quoted, it must not be elided
> >
> > I don't think that is correct. In fact "$e" *must* be elided -
> > because you juxtaposed it with the next token. eliding and quoting are orthogonal.
>
> Your statement is confusing to me. Here, in more detail, is exactly
> what I meant (and what I though I implied in the first case):
>
> ...
>
> Because "$e" is quoted, the resulting empty string must not be elided
> during word splitting.
>
I see - thanks. I was not aware of that effect of quoting.
But I see you are correct.
>
> ...
>
> Why do you find that interesting? There is NO word splitting in
> assignment contexts, so the effect of
Again I stand corrected, thanks. I thought an unquoted blank would terminate an assignment value.
Maybe I was confusing tokenization before substitution with word splitting after substitution.
next prev parent reply other threads:[~2010-08-04 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100803203204.GG13690@gmx.de>
2010-08-03 20:55 ` Eric Blake
2010-08-03 21:21 ` Mikael Magnusson
2010-08-03 21:28 ` Eric Blake
2010-08-04 15:18 ` John Lumby
2010-08-04 15:27 ` Eric Blake
2010-08-04 17:06 ` John Lumby [this message]
2010-08-03 21:43 ` Peter Stephenson
2010-08-05 22:15 ` Chet Ramey
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=COL116-W22D62FDC242BA2072A0328A3AF0@phx.gbl \
--to=johnlumby@hotmail.com \
--cc=autoconf@gnu.org \
--cc=eblake@redhat.com \
--cc=zsh-workers@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).