Re: Syntax question

2007-03-24 Thread Paul Jarc
"Caleb Cushing" <[EMAIL PROTECTED]> wrote: > the line > FEATURES="parallel-fetch ccache distlocks"# userfetch userpriv usersandbox > > I was told my bug is not a bug because there was no space in between the "# > > putting a space does fix the problem but I can't recall that I've ever seen > any do

Syntax question

2007-03-24 Thread Caleb Cushing
sorry if this is an unwelcome question here... I recently reported a bug to my distribution and was told it was not a bug. I'm wondering about the standard behavior of comments in bash. I've always been told that a comment start's with # and that everything after it is a comment it. the line FEA

Re: variable assignments and parameter expansion in a single command

2007-03-24 Thread Chet Ramey
Kevin F. Quinn wrote: > On Sat, 24 Mar 2007 14:23:39 -0400 > Chet Ramey <[EMAIL PROTECTED]> wrote: > >> Mike Frysinger wrote: >>> i'm trying to determine whether POSIX allows for utilizing of >>> variables in simple commands that were defined earlier in the same >>> command ... in other words, whe

Re: variable assignments and parameter expansion in a single command

2007-03-24 Thread Kevin F. Quinn
On Sat, 24 Mar 2007 14:23:39 -0400 Chet Ramey <[EMAIL PROTECTED]> wrote: > Mike Frysinger wrote: > > i'm trying to determine whether POSIX allows for utilizing of > > variables in simple commands that were defined earlier in the same > > command ... in other words, whether this snippet: > > unset

Patch to Bash man page to explain new semantics of quoted regexps for the =~ operator

2007-03-24 Thread Fran Litterio
The below patch to the Bash man page adds some prose to explain the recent change to how regular expressions are parsed with the =~ operator. I hope this helps. One of the lines in the patch is kind of long. I could not figure out how to break it in a way that did not mess up the appearance of t

Re: variable assignments and parameter expansion in a single command

2007-03-24 Thread Chet Ramey
Mike Frysinger wrote: > i'm trying to determine whether POSIX allows for utilizing of variables in > simple commands that were defined earlier in the same command ... in other > words, whether this snippet: > unset A B > A="moo" B="$A more" > echo $A , $B > should display moo twice or just once:

Re: variable assignments and parameter expansion in a single command

2007-03-24 Thread Andreas Schwab
Mike Frysinger <[EMAIL PROTECTED]> writes: > i'm trying to determine whether POSIX allows for utilizing of variables in > simple commands that were defined earlier in the same command ... in other > words, whether this snippet: > unset A B > A="moo" B="$A more" > echo $A , $B > should display mo

variable assignments and parameter expansion in a single command

2007-03-24 Thread Mike Frysinger
i'm trying to determine whether POSIX allows for utilizing of variables in simple commands that were defined earlier in the same command ... in other words, whether this snippet: unset A B A="moo" B="$A more" echo $A , $B should display moo twice or just once: moo , moo more moo , more my readi