Phil Pennock wrote:
> On 2008-01-04 at 16:07 -0800, Michael G Schwern wrote:
>> Of course, as Peter insinuated, I'm sure by now it's been rationalized as a
>> "feature".
>
> In large environments, having everything always locally available on
> local disk is fairly recent, with cluster management
On 2008-01-04, at 18:43, Phil Pennock wrote:
ObHate: These two don't produce the same result:
$functions['foo bar']
x='foo bar'; $functions[$x]
I think I know why, and if so that's probably the only "C" like
feature in csh. Typical that zsh would decide that was something to
inherit fro
On 2008-01-04 at 20:33 +, Aaron Crane wrote:
> Also, I decided I didn't care about any brokenness resulting from
> however the user might have managed to persuade the shell to create a
> function with a non-identifier-syntax name. After all:
>
> $ foo\ bar() { echo blah; }
> -bash: `foo\
On 2008-01-04 at 16:07 -0800, Michael G Schwern wrote:
> Of course, as Peter insinuated, I'm sure by now it's been rationalized as a
> "feature".
In large environments, having everything always locally available on
local disk is fairly recent, with cluster management systems etc. NFS
is still com
Smylers wrote:
> I just spotted this in the README.Debian that Debian supply with Bash:
>
> bash does not check $PATH if hash fails
>
> bash hashes the location of recently executed commands. When a command
> is moved to a new location in the PATH, the command is still in the
> PATH but t
