Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: x[
Date: Mon, 29 Jul 2019 18:53:38 +0100
Lines: 31
Approved: bug-bash@gnu.org
Message-ID: <mailman.173.1564422827.1985.bug-bash@gnu.org>
References: <CAAZkfoK2hYq_qSkdKYc1on=+V4VEBgpgZW96sYNZwC+AMw7iTw@mail.gmail.com> <mailman.158.1564419372.1985.bug-bash@gnu.org> <20190729175338.ewjhkqxcmnm3q3km@chaz.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: bug-bash <bug-bash@gnu.org>
To: Isabella Bosia <izaberina@gmail.com>
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <mailman.158.1564419372.1985.bug-bash@gnu.org>
User-Agent: NeoMutt/20171215
Precedence: list
Xref: csiph.com gnu.bash.bug:15264

2019-07-29 17:55:58 +0100, Isabella Bosia:
> haven't really looked into why this happens but x[ seems to trigger some
> funny parser behavior
> 
> x[ newline     should not prompt with PS2
> 
> it can't be defined as a normal sh function, but it can be defined with the
> function keyword
[...]

x[ is the start of an array element assignment. newline is valid (just a token
separator like space) inside an arithmetic expression.

$ x[
> 1
> +
> 1
> ]=3
$ typeset -p x
declare -a x=([2]="3")

You'll notice:

$ +[
+[: command not found
$ 'x'[
x[: command not found

-- 
Stephane