Thanks for your reply. That would certainly help.
Regards,
Ken
-Original Message-
From: Chet Ramey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 9:51 PM
To: Ken Failbus
Cc: Andreas Schwab; bug-bash@gnu.org; [EMAIL PROTECTED]
Subject: Re: bash -n doesn't seem to catc
, October 16, 2007 10:14 AM
To: Ken Failbus
Cc: bug-bash@gnu.org
Subject: Re: bash -n doesn't seem to catch all syntax errors...
"Ken Failbus" <[EMAIL PROTECTED]> writes:
> bash -x /tmp/mydummy
> + shopt -s extglob
> + rm -f '/tmp/file.+([0-9])'
> + ex
his.
Thanks & Regards,
Ken
-Original Message-
From: Ken Failbus
Sent: Tuesday, October 16, 2007 6:47 AM
To: Stephane Chazelas
Cc: bug-bash@gnu.org
Subject: RE: bash -n doesn't seem to catch all syntax errors...
Hi Guys,
I understand that the example I provided is valid, use t
with a good bad example.
That way I would be heading in the right direction.
Ken
-Original Message-
From: Stephane Chazelas [mailto:[EMAIL PROTECTED]
Sent: Tue 10/16/2007 3:08 AM
To: Ken Failbus
Cc: bug-bash@gnu.org
Subject: Re: bash -n doesn't seem to catch all syntax errors...
Hi Guys,
When I specify on command-line "bash -n ". Bash doesn't
check for valid syntax errors. E.g. if variable is missing a "$" infront
of it while assigning a value. This is not catched by bash. Is there a
more specific option that should be specified to bash to check for
syntax errors.
Regard
lto:[EMAIL PROTECTED]
Sent: Friday, October 12, 2007 5:07 PM
To: Ken Failbus
Cc: bug-bash@gnu.org; [EMAIL PROTECTED]
Subject: Re: bash script in background gets interrupted if carriage
return is hit...
Ken Failbus wrote:
> I have a script that when run in background and while it's r
Hi,
I have a script that when run in background and while it's running
hitting a carriage return causes it's to completely stop the script and
the terminal in which it's running disappears. It seems as though it
received a interrupt signal. Is there some kind of a job control or
terminal keys gett
