From: Mark Lentczner <mark@glyphic.com>
To: dash@vger.kernel.org
Subject: Parameter substitution bug
Date: Mon, 21 Jan 2013 13:36:07 -0800 [thread overview]
Message-ID: <CAPnksqRxUvwGGQwXBPVj-yrA8a18nmLctZGD0BtBnh_vC-Muhg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Strangely I ran across this issue in the real world: A doubly nested
parameter substitution with an inner glob pattern (breath) fails /only
when in double quotes/! That is, these two expressions produce
different results:
${f%${f#?}} --vs-- "${f%${f#?}}"
Strangely, that is the simplest case I get to fail.
The following script walks through the issue, and if run with bash,
ksh, or busybox exhibits those two expressions as producing the same
result.
- Mark
(Note: Not on mailing list, so please reply all to include me!)
[-- Attachment #2: dash-bug.sh --]
[-- Type: application/x-sh, Size: 1616 bytes --]
next reply other threads:[~2013-01-21 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 21:36 Mark Lentczner [this message]
2013-08-23 10:49 ` Parameter substitution bug Herbert Xu
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=CAPnksqRxUvwGGQwXBPVj-yrA8a18nmLctZGD0BtBnh_vC-Muhg@mail.gmail.com \
--to=mark@glyphic.com \
--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;
as well as URLs for NNTP newsgroup(s).