Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15261
| From | Clint Hepner <clint.hepner@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: x[ |
| Date | 2019-07-29 13:01 -0400 |
| Message-ID | <mailman.161.1564419701.1985.bug-bash@gnu.org> (permalink) |
| References | <CAAZkfoK2hYq_qSkdKYc1on=+V4VEBgpgZW96sYNZwC+AMw7iTw@mail.gmail.com> <9EA25AF1-6D80-456A-81FA-6D908072E624@gmail.com> |
> On 2019 Jul 29 , at 12:55 p, Isabella Bosia <izaberina@gmail.com> wrote: > > 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 > > it can't be called like a normal function, but things like "x[" or \x[ work > > 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.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: x[ Clint Hepner <clint.hepner@gmail.com> - 2019-07-29 13:01 -0400
csiph-web