Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15261 > unrolled thread
| Started by | Clint Hepner <clint.hepner@gmail.com> |
|---|---|
| First post | 2019-07-29 13:01 -0400 |
| Last post | 2019-07-29 13:01 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: x[ Clint Hepner <clint.hepner@gmail.com> - 2019-07-29 13:01 -0400
| From | Clint Hepner <clint.hepner@gmail.com> |
|---|---|
| Date | 2019-07-29 13:01 -0400 |
| Subject | Re: x[ |
| Message-ID | <mailman.161.1564419701.1985.bug-bash@gnu.org> |
> 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 top | Article view | gnu.bash.bug
csiph-web