Re: set -n ruins shell

[George Herson]

Paul Jarc wrote:

> George Herson <gherson@snet.net> wrote:
>
> > Thanks, but why am i still getting zero output?
> >
> > [root@geodollar /root]# bash -c 'set -n; . /tmp/tmpscript'
> > [root@geodollar /root]# chmod u+x /tmp/tmpscript
> > [root@geodollar /root]# bash -n /tmp/tmpscript
> > [root@geodollar /root]#
>
> Because with -n, the commands aren't executed.  So bash doesn't notice
> if a command doesn't exist.
>
>
> > Should i try a "real" syntax error?  like what?
>
> That should produce an error message.  Try this:
> echo (hello
>
>
> paul
Paul Jarc <prj@po.cwru.edu>



$ bash -c 'set -n; . /tmp/tmpscript2'
$ bash -n /tmp/tmpscript2
/tmp/tmpscript2: line 1: syntax error near unexpected token `(hello'
/tmp/tmpscript2: line 1: `echo (hello'


Thanks.  The first form didn't have output but the second did.

george