Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14197
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Clarify cases of implicit and explicit line continuation |
| Date | 2018-06-01 08:48 -0400 |
| Message-ID | <mailman.930.1527857327.1292.bug-bash@gnu.org> (permalink) |
| References | <CAH-HCWWkjs-tzA19zbFto00ptfvV4tGB+Ks3SzyxPhYpnOgWhA@mail.gmail.com> |
On 6/1/18 1:28 AM, Shriramana Sharma wrote: > Hello. See https://unix.stackexchange.com/questions/253518/where-are-bash-line-continuations-after-and-documented. > > Roughly put, wherever lines terminating with a particular token are > syntactically valid, they are taken as complete, and an explicit \ is > required to continue the line, but lines ending with && || or I and > lines where an array definition has been started with =( but not > closed with a ) implicitly continue to the next physical line. 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. -- ``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 gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Clarify cases of implicit and explicit line continuation Chet Ramey <chet.ramey@case.edu> - 2018-06-01 08:48 -0400
csiph-web