Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14221 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-06-05 09:17 -0400 |
| Last post | 2018-06-05 09:17 -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: Clarify cases of implicit and explicit line continuation Chet Ramey <chet.ramey@case.edu> - 2018-06-05 09:17 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-06-05 09:17 -0400 |
| Subject | Re: Clarify cases of implicit and explicit line continuation |
| Message-ID | <mailman.1198.1528204661.1292.bug-bash@gnu.org> |
On 6/4/18 10:20 PM, Shriramana Sharma wrote: > On Fri, Jun 1, 2018 at 6:18 PM, Chet Ramey <chet.ramey@case.edu> wrote: >> The general rule is simple: bash reads input a line at a time, feeding >> each line to the parser, until it has enough input for a complete >> command. If it doesn't have enough to complete a command, it will read >> additional lines. If a newline would complete a command, you need to >> quote it to prevent it being interpreted as such. > > Yes that is all understood. All I'm requesting for is for this > behaviour to be *documented* in the manpage. I understand. I don't think it adds much to the documentation to describe in such basic terms the fundamental operation of the shell: that it reads lines from its input source until it assembles a complete command, then executes it. This is just what shells do. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web