Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Clint Hepner <clint.hepner@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: x[
Date: Mon, 29 Jul 2019 13:01:35 -0400
Lines: 26
Approved: bug-bash@gnu.org
Message-ID: <mailman.161.1564419701.1985.bug-bash@gnu.org>
References: <CAAZkfoK2hYq_qSkdKYc1on=+V4VEBgpgZW96sYNZwC+AMw7iTw@mail.gmail.com> <9EA25AF1-6D80-456A-81FA-6D908072E624@gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: bug-bash <bug-bash@gnu.org>
To: Isabella Bosia <izaberina@gmail.com>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAAZkfoK2hYq_qSkdKYc1on=+V4VEBgpgZW96sYNZwC+AMw7iTw@mail.gmail.com>
Precedence: list
Xref: csiph.com gnu.bash.bug:15261



> On 2019 Jul 29 , at 12:55 p, Isabella Bosia <izaberina@gmail.com> =
wrote:
>=20
> haven't really looked into why this happens but x[ seems to trigger =
some
> funny parser behavior
>=20
> x[ newline     should not prompt with PS2
>=20
> it can't be defined as a normal sh function, but it can be defined =
with the
> function keyword
>=20
> it can't be called like a normal function, but things like "x[" or \x[ =
work
>=20
> this bug seems old


The ``[`` begins a valid shell pattern, so the parser continues to =
accept input until the closing ``]`` is found. Pathname expansion =
(apparently) does not apply to the first "argument" of the ``function`` =
command.=