Re: [PATCH] Ensure the command found in the hash table exists, not only on POSIXLY_CORRECT

On 1/7/10 5:30 PM, Giuseppe Scrivano wrote: > the code I have attached is just a test case that actually, AFAICS, > can't be fixed without change its code. This situation can be present > in a shell script that potentially can rely on the PATH elements > precedence. > > Is there a way to disable

Re: [PATCH] Ensure the command found in the hash table exists, not only on POSIXLY_CORRECT

Thanks for your answer. Chet Ramey writes: >> I have a question: how bash should behave in the case you have: >> >> --- >> export PATH=a:b:$PATH >> >> mkdir a b >> >> cat > b/prog.sh << EOF >> echo b/prog.sh >> EOF >> >> chmod +x b/prog.sh >> >> prog

Re: [PATCH] Ensure the command found in the hash table exists, not only on POSIXLY_CORRECT

On 1/7/10 8:39 AM, Giuseppe Scrivano wrote: > Hello, > > what do you think about make this the default behavior, not only when > POSIXLY_CORRECT is specified? A `stat' is very fast, the cost of a > stat+fork+exec is almost the same of a fork+exec. If you want to make this your default behavior,

[PATCH] Ensure the command found in the hash table exists, not only on POSIXLY_CORRECT

tter is the hashed value. Thanks, Giuseppe Scrivano >From c786059d65fc47d6265ebde3fe88c18c381dc77b Mon Sep 17 00:00:00 2001 From: Giuseppe Scrivano Date: Thu, 7 Jan 2010 13:52:13 +0100 Subject: [PATCH] Ensure the command found in the hash table exists, not only on POSIXLY_CORRECT --- f