Re: Confused about how bash breaks input into words

2010-02-24 Thread Marc Herbert
Eric Blake a écrit : > > Another good reference is POSIX: > http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_03 A less rigorous and easier reading is the Guide to Unix Shell Quoting:

Re: Confused about how bash breaks input into words

2010-02-23 Thread DennisW
On Feb 23, 8:41 pm, Allen Halsey wrote: > Eric Blake redhat.com> writes: > > > > > But you missed that: > > > $(date +'%Y-%m-%d') > > > is an entire word (basically, an unquoted $ character consumes until the > > end of the shell substitution, command substitution, or arithmetic > > substitution,

Re: Confused about how bash breaks input into words

2010-02-23 Thread Allen Halsey
Eric Blake redhat.com> writes: > > But you missed that: > > $(date +'%Y-%m-%d') > > is an entire word (basically, an unquoted $ character consumes until the > end of the shell substitution, command substitution, or arithmetic > substitution, and that entire scan becomes part of the current word

Re: Confused about how bash breaks input into words

2010-02-23 Thread Chris F.A. Johnson
On Tue, 23 Feb 2010, Eric Blake wrote: > According to Allen Halsey on 2/23/2010 3:50 PM: > > Hi, > > > > I'm trying to understand bash's parsing model. > > > > I read in the manual that the shell "breaks the input into words and > > operators, > > obeying the quoting rules described in Quoting.

Re: Confused about how bash breaks input into words

2010-02-23 Thread Eric Blake
According to Allen Halsey on 2/23/2010 3:50 PM: > Hi, > > I'm trying to understand bash's parsing model. > > I read in the manual that the shell "breaks the input into words and > operators, > obeying the quoting rules described in Quoting. These tokens are separated by > metacharacters." Anoth