Remind me about oddball reserved words

Remind me about oddball reserved words

[Bart Schaefer]

Here's the entire (11 lines) doc for reserved words:

##
6.5 Reserved Words
==================

The following words are recognized as reserved words when used as the
first word of a command unless quoted or disabled using disable -r:

do done esac then elif else fi for case if while function repeat time
until select coproc nocorrect foreach end ! [[ { }

Additionally, `}' is recognized in any position if neither the
IGNORE_BRACES option nor the IGNORE_CLOSE_BRACES option is set.
##

Close brace is recognized as a reserved word in command position?  I've
entirely forgotten why and would like to be reminded.  Also, why close
brace and not close-double-bracket?

Re: Remind me about oddball reserved words

[Peter Stephenson]

On Sat, 28 Mar 2015 14:58:51 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Close brace is recognized as a reserved word in command position?  I've
> entirely forgotten why and would like to be reminded.

I would guess it's to do with the fact that with IGNORE_BRACES (or
IGNORE_CLOSE_BRACES) set, which is old sh style, "}" needs to be in
command position.  I suspect it's not needed in native mode.

> Also, why close brace and not close-double-bracket?

There's no case where ']]' needs to be special in command position, only
at the end of a specially parsed condition.

pws

Re: Remind me about oddball reserved words

[Bart Schaefer]

On Mar 28, 10:39pm, Peter Stephenson wrote:
} Subject: Re: Remind me about oddball reserved words
}
} On Sat, 28 Mar 2015 14:58:51 -0700
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > Close brace is recognized as a reserved word in command position?  I've
} > entirely forgotten why and would like to be reminded.
} 
} I would guess it's to do with the fact that with IGNORE_BRACES (or
} IGNORE_CLOSE_BRACES) set, which is old sh style, "}" needs to be in
} command position.

$ { echo Ahh, yes, that is exactly it.; echo Thanks.; }