On 5/30/10 4:22 AM, Jan Schampera wrote:
> If this is not a bug, what's the reason behind this? Is it to blindly
> report success when an operand "looks like a pathname"?
`hash' ignores operands with slashes. It just doesn't consider them at
all. They don't get into the hash table and they don'
Jan Schampera writes:
> If this is not a bug, what's the reason behind this?
Probably because a command name containing a slash is never looked up on
$PATH, thus never remembered and put in the hash table.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53
Hello Chet,
hello list,
during some discussion in the IRC #bash channel on freenode we found a
weird behaviour of the 'hash' builtin command.
The command exits true if the operand in question contains a /, no
matter if that makes sense or not:
---
$ hash
'CHANGELOG_CURRENT="http://slackwa
