From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Max Kirillov <max@max630.net>, Carlo Arenas <carenas@gmail.com>,
Jeff King <peff@peff.net>,
git@vger.kernel.org
Subject: Re: [PATCH] test-lib: check Bash version for '-x' without using shell arrays
Date: Thu, 3 Jan 2019 12:36:59 +0100 [thread overview]
Message-ID: <20190103113659.GA4673@szeder.dev> (raw)
In-Reply-To: <20190101231949.8184-1-szeder.dev@gmail.com>
On Wed, Jan 02, 2019 at 12:19:49AM +0100, SZEDER Gábor wrote:
> To my understanding both shells are right and conform to POSIX,
> because the standard allows both behavior by stating the following
> under '2.8.1 Consequences of Shell Errors':
>
> "An expansion error is one that occurs when the shell expansions
> define in wordexp are carried out (for example, "${x!y}", because
That "define" above always stops my (non-native) English parser for a
moment or two... shouldn't it be s/define/defined/ ?
It's not a copy-paste error, POSIX does indeed write "define" there,
see:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_01
(First paragraph below the table and the Notes.)
> '!' is not a valid operator); an implementation may treat these as
> syntax errors if it is able to detect them during tokenization,
> rather than during expansion."
>
prev parent reply other threads:[~2019-01-03 11:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 23:19 [PATCH] test-lib: check Bash version for '-x' without using shell arrays SZEDER Gábor
2019-01-02 0:20 ` Johannes Sixt
2019-01-02 16:46 ` Junio C Hamano
2019-01-03 11:43 ` [PATCH v2] " SZEDER Gábor
2019-01-03 20:29 ` Junio C Hamano
2019-01-04 9:30 ` SZEDER Gábor
2019-01-04 11:25 ` Junio C Hamano
2019-01-04 12:38 ` SZEDER Gábor
2019-01-04 18:42 ` Carlo Arenas
2019-01-04 20:04 ` Junio C Hamano
2019-01-03 4:52 ` [PATCH] " Jeff King
2019-01-02 18:05 ` Eric Sunshine
2019-01-02 18:31 ` Carlo Arenas
2019-01-03 11:36 ` SZEDER Gábor [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190103113659.GA4673@szeder.dev \
--to=szeder.dev@gmail.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@max630.net \
--cc=peff@peff.net \
/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://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).