Hi Chet,
On 2014-03-18 08:58, Chet Ramey wrote:
On 3/18/14 2:23 AM, Filipus Klutiero wrote:
Package: bash
Version: 4.3-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: bug-b...@gnu.org
According to the section Compound Commands of the manual page, a compound
command is one of 11 forms listed. However, as explained in the ALIASES
section, a function definition ( function name [()] compound-command
[redirection] ) is also a compound command.
A function definition is a function definition command. The sentence
in the ALIASES section should read "a function definition is itself a
command."
Ah, indeed. In this case, this report is invalid. Feel free to close it (I'll
open a new ticket if the source issue persists).
Multiple other forms of compound commands are not documented, for example {
if true; then echo x; fi }.
I'm not sure what this means. Group commands are compound commands, and
are documented as such.
If you want to take a look at the Posix grammar and list of compound
commands, go to
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_04
Thank you
What's the point of this report? Is there some problem this is attempting
to address?
Sorry for the last paragraph, I didn't realize that "if true; then echo x; fi"
was a list. Thanks, the definition of compound commands is OK then. I probably developed
my misunderstanding of what a list is due to the order of sections and the fact that the
manpage does not define what a command is. To be fair, even the author of the info
documentation got that wrong:
A `pipeline' is a sequence of simple commands separated by one of the
control operators `|' or `|&'.
--
Filipus Klutiero
http://www.philippecloutier.com
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
