Re: Time delay on command not found

2011-10-10 Thread Pierre Gaston
On Tue, Oct 11, 2011 at 3:38 AM, Bill Gradwohl wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > when I typo a command, bash comes back with a command not found but > hangs the terminal for way too long. > > How do I get rid of the delay. I want it to release the terminal > immediately

[patch] jobs.c not checking HAVE_SYS_PARAM_H

2011-10-10 Thread John E. Malmberg
In the bash 4.2 source: jobs.c is not checking HAVE_SYS_PARAM_H. This prevents it from compiling on VMS which does not supply this header. Regards, -John wb8tyw@qsl.network Personal Opinion Only $ diff -ub a/jobs.c b/jobs.c --- a/jobs.c 2011-09-26 22:28:17.0 -0500 +++ b/jobs.c

Re: Time delay on command not found

2011-10-10 Thread Bob Proulx
Bill Gradwohl wrote: > when I typo a command, bash comes back with a command not found but > hangs the terminal for way too long. When you try to launch a command that does not exist anywhere on PATH then bash must search every directory component of PATH in order to look for the command. > How d

Time delay on command not found

2011-10-10 Thread Bill Gradwohl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 when I typo a command, bash comes back with a command not found but hangs the terminal for way too long. How do I get rid of the delay. I want it to release the terminal immediately. - -- Bill Gradwohl Roatan, Honduras -BEGIN PGP SIGNATURE-

Re: [patch] fix parallel build issues with parse.y

2011-10-10 Thread Chet Ramey
On 10/7/11 3:53 PM, Mike Frysinger wrote: > the current yacc rules allow multiple runs to generate the same files. > usually > this doesn't come up as the generated files are shipped in the tarball, but > when you modify parse.y (applying a patch or developing or whatever), you can > hit this pro

Re: exported SHELLOPTS gives error message from sh

2011-10-10 Thread Chet Ramey
> On Mon, Oct 10, 2011 at 11:06:16AM -0400, Len Giambrone wrote: > > I understand that. But if you change all your scripts to use > > > > #!/bin/bash > > instead of > > #!/bin/sh > > > > your scripts will fail when bash isn't installed. > > If you use bash features in your script, then you must

Re: Bash does not like DOS file format

2011-10-10 Thread Eric Blake
On 10/05/2011 02:37 PM, Russ Browne wrote: > Configuration Information [Automatically generated, do not change]: > > Machine: i686 > > OS: cygwin > > Compiler: gcc-4 > > Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' > -DCONF_OSTYPE='cygwin' Given that you are trying to use c

Re: exported SHELLOPTS gives error message from sh

2011-10-10 Thread Greg Wooledge
On Mon, Oct 10, 2011 at 11:06:16AM -0400, Len Giambrone wrote: > I understand that. But if you change all your scripts to use > > #!/bin/bash > instead of > #!/bin/sh > > your scripts will fail when bash isn't installed. If you use bash features in your script, then you must ensure that the scr

Re: exported SHELLOPTS gives error message from sh

2011-10-10 Thread Len Giambrone
I understand that. But if you change all your scripts to use #!/bin/bash instead of #!/bin/sh your scripts will fail when bash isn't installed. -Len On Oct 10, 2011, at 8:24 AM, Greg Wooledge wrote: On Thu, Oct 06, 2011 at 02:54:56PM -0400, Len Giambrone wrote: Many people now use sh and b

Re: exported SHELLOPTS gives error message from sh

2011-10-10 Thread Greg Wooledge
On Thu, Oct 06, 2011 at 02:54:56PM -0400, Len Giambrone wrote: > Many people now use sh and bash interchangeably. That is wrong. Those people need to learn that sh and bash are NOT interchangeable.