From: Harald van Dijk <harald@gigawatt.nl>
To: dash@vger.kernel.org
Subject: Quoted closing brace in variable default expansion
Date: Sat, 13 Nov 2010 17:27:15 +0059 [thread overview]
Message-ID: <4CDEBC7B.5050805@gigawatt.nl> (raw)
Hi all,
It's probably best to start with the example:
$ bash -c 'echo "${x:-"}"}"'
}
$ ksh -c 'echo "${x:-"}"}"'
}
$ dash -c 'echo "${x:-"}"}"'
dash: 1: Syntax error: Unterminated quoted string
$ busybox sh -c 'echo "${x:-"}"}"'
sh: syntax error: unterminated quoted string
It looks like dash and other ash derivatives stop the expansion with the
first }, instead of the first unquoted }. I'm getting confused trying to
figure out whether this is a bug in dash or in the script relying on it.
A slightly modified example:
$ dash -c 'echo "${x-"_{x}_"}"'
dash: 1: Syntax error: Unterminated quoted string
$ dash -c 'echo ${x-"_{x}_"}'
_{x_}
I don't understand how the last line works. The } is printed after the
_, so the } that is printed must be the final }, and the } directly
following the x stops the variable default. But this would lead to two
double quote characters which have no way of matching up, yet no syntax
error is given.
Could you clarify?
Cheers,
Harald
next reply other threads:[~2010-11-13 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 16:28 Harald van Dijk [this message]
2010-11-13 16:41 ` Quoted closing brace in variable default expansion Jonathan Nieder
2010-11-13 17:29 ` Harald van Dijk
2010-11-19 13:54 ` Herbert Xu
2010-11-20 0:43 ` Harald van Dijk
2010-11-20 20:57 ` Cristian Ionescu-Idbohrn
2010-11-21 13:42 ` [PATCH] [PARSER] Remove backslash before } in double-quotes in variable Jilles Tjoelker
2010-11-21 16:35 ` Jonathan Nieder
2010-11-23 18:46 ` Harald van Dijk
2011-03-10 8:59 ` Herbert Xu
2011-03-11 18:32 ` Jilles Tjoelker
2010-11-13 17:51 ` Quoted closing brace in variable default expansion Jilles Tjoelker
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=4CDEBC7B.5050805@gigawatt.nl \
--to=harald@gigawatt.nl \
--cc=dash@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox