From: Olof Johansson <olof@ethup.se>
To: Harald van Dijk <harald@gigawatt.nl>, dash@vger.kernel.org
Subject: Re: Parameter expansion, patterns and fnmatch
Date: Wed, 17 Aug 2016 16:50:33 +0200 [thread overview]
Message-ID: <20160817145033.GE23983@brutus.ethup.se> (raw)
In-Reply-To: <0ce0bca2-3bdd-a1f5-169e-0291a49cd6c7@gigawatt.nl>
On 2016-08-09 23:39 +0200, Harald van Dijk wrote:
> Yes, this looks like a bug in dash. With the default
> --disable-fnmatch code, when dash encounters [ in a pattern, it
> immediately treats the following characters as part of the set. If
> it then encounters the end of the pattern without having seen a
> matching ], it attempts to reset the state and continue as if [ was
> treated as a literal character right from the start. The attempt to
> reset the state doesn't look right, and has been like this since at
> least the initial Git commit in 2005.
>
> This also affects
>
> case [a in [?) echo ok ;; *) echo bad ;; esac
>
> which should print ok.
>
> Attached is a patch that attempts to reset the state correctly. It
> passes your test and mine, but I have not yet tested it extensively.
Thanks a lot! For what it's worth, I've been using dash with this
patch this for about a week now, including building a lot of open
source software (via OpenEmbedded). I haven't seen any issues yet.
--
Olof Johansson https://github.com/olof
next prev parent reply other threads:[~2016-08-17 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 9:28 Parameter expansion, patterns and fnmatch Olof Johansson
2016-08-09 21:39 ` Harald van Dijk
2016-08-17 14:50 ` Olof Johansson [this message]
2016-09-02 14:04 ` Herbert Xu
2016-09-02 14:25 ` Eric Blake
2016-09-02 14:29 ` Herbert Xu
2016-09-02 14:49 ` Eric Blake
2016-09-02 14:51 ` Herbert Xu
2016-09-03 12:03 ` Harald van Dijk
2016-09-03 13:05 ` Herbert Xu
2016-09-03 13:19 ` Harald van Dijk
2016-09-03 13:58 ` Herbert Xu
2016-09-03 15:16 ` Harald van Dijk
2016-09-02 14:46 ` Herbert Xu
2016-09-02 14:54 ` Eric Blake
2016-09-02 15:06 ` Chet Ramey
2016-09-02 14:48 ` Eric Blake
2016-09-02 15:12 ` 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=20160817145033.GE23983@brutus.ethup.se \
--to=olof@ethup.se \
--cc=dash@vger.kernel.org \
--cc=harald@gigawatt.nl \
/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