GNU bash, version 3.00.15(1)-release (i686-redhat-linux-gnu)
Is what I am describing a bug, or lack of understanding?
There are three examples here. If executable file is in cwd and path
points to cwd and if the same file is referenced bash executes a file
that is outside of the cwd! This to me
I have learned a lot from your reply, and yes some of what you wrote
explains this as not being a bug; after a reboot I cannot reproduce
these results.
On Tue, 2007-01-02 at 10:50 -0700, Bob Proulx wrote:
> Did you previously reference the file and have that path cached?
mycmd was created using
On Wed, 2007-01-03 at 22:55 -0700, Bob Proulx wrote:
> > I have learned a lot from your reply, and yes some of what you wrote
> > explains this as not being a bug; after a reboot I cannot reproduce
> > these results.
>
> You should not need to reboot to clear a single shell process hash
> cache.
On Thu, 2007-01-04 at 11:31 -0700, Bob Proulx wrote:
> Bojan Land wrote:
> > Bob Proulx wrote:
> > > This is possible when it has been cached by bash and then the
> > > executable is either moved from its original location or a new
> > > executable appears earl
On Fri, 2007-01-05 at 11:05 -0800, Matthew Woehlke wrote:
> (Next time, reply to the list, please! Which means send any replies to
> this message to bug-bash...)
I clicked on reply to all, seems you didn't include the list in your
response previously nor this time! I've included the list now but
Eric beat me to this. :-) Odd that 'reply all' didn't work for you...
ah, but now I understand why (see below). Anyway, last time I
intentionally did not redirect to the list. I make it policy to
indicate that you should do that, otherwise I am publicly re-posting a
private correspondence witho
