Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15071 > unrolled thread

Suggestion that might help clarify meaning

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.

Contents

  Suggestion that might help clarify meaning Gavin Rebeiro <gavin.rebeiro1@googlemail.com> - 2019-06-24 18:25 +0100

#15071 — Suggestion that might help clarify meaning

Hi,

I've been searching the BASH manual (
https://www.gnu.org/software/bash/manual/bash.html) to find out about the
precedence/sequence that the shell parses commands. The particular question
I've had which I was helped with:
https://unix.stackexchange.com/questions/526646/precedence-of-subshells-in-relation-to-redirection
.

May I request a slight edit in the sentence from section 3.7.1 Simple
Command Expansion:

"When a simple command is executed, the shell performs the following
expansions, assignments, and redirections, from left to right. "

to something like:

"When a simple command is executed, the shell performs the following
expansions, assignments, and redirections, from left to right, in the
following sequence."

or

"When a simple command is executed, the shell performs the following
expansions, assignments, and redirections, from left to right, with the
following precedence. "

As this makes it a bit more explicit that the following list gives a
sequence/precedence that tells us the order in which commands are parsed.
The intended meaning wasn't fully clear to me upon first reading and I
believe that this would make the documentation more readable and might
prevent cases of similar confusion.

Best wishes,
Gavin Rebeiro

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web