Re: parse error running builtins from array

mk27 writes: >>Take a look at the arguments you are actually using: > > [root~] printf "%s" ${cc[1]} > bash-c"timels-l" > > Again, I can't see the missing " Try your original example after set -x. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756

Re: parse error running builtins from array

On Wed, 29 Jul 2009, mk27 wrote: > >Take a look at the arguments you are actually using: > > [root~] printf "%s" ${cc[1]} > bash-c"timels-l" > > Again, I can't see the missing " Try using the code I posted: printf "%s\n" ${cc[1]} -- Chris F.A. Johnson, webmaster

Re: parse error running builtins from array

>Take a look at the arguments you are actually using: [root~] printf "%s" ${cc[1]} bash-c"timels-l" Again, I can't see the missing " >use eval I didn't know the shell had an eval so that solves that! Much thanks. -- View this message in context:

Re: parse error running builtins from array

On Tue, 28 Jul 2009, mk27 wrote: > > cc=('who' 'bash -c "time ls -l"' 'date') > > for e in 0 1 2; do ${cc[$e]}; done > > produces an error: > ls: -c: line 0: unexpected EOF while looking for matching `"' > ls: -c: line 1: syntax error: unexpected end of file > > well, there isn't a missing " A

parse error running builtins from array

g " AFAICT, and playing around with them has not helped. Does anyone have a way out of this? -- View this message in context: http://www.nabble.com/parse-error-running-builtins-from-array-tp24705077p24705077.html Sent from the Gnu - Bash mailing list archive at Nabble.com.