Bash lets me work every day, despite its shortcomings.
Just start me on Finder.
Neil
PS and top posting.
On 19 Oct 2010, at 00:02, Daniel Pittman <[email protected]> wrote:
Nicholas Clark <[email protected]> writes:
Dear bash,
Why do you insist on hashing the paths to commands.
And never expiring the cache.
Or detecting that it has gone stale.
In this day and age, of more RAM and CPU than we know what to do with?
How hard would it be to record the device, inode and mtime of each entry in
PATH, and automatically flush the cache if any change?
Not hard, really.
That's what I find hateful.
What I find hateful is the "Don't Be Stupid" switch. Which, naturally, the
developers of bash supplied because you wouldn't want to surprise people by
changing this monumentally stupid ^W historic behaviour.
So, instead, we have 'set -o checkhash' to ask it to please work like sane
people expect.
Which, of course, accompanies the other half dozen "Don't Be Stupid" options
I have configured in my shell setup to ensure it doesn't suck quite as much.
Daniel
--
X Windows is the Iran-Contra of graphical user interfaces: a tragedy of
political compromises, entangled alliances, marketing hype, and just plain
greed. X Windows is to memory as Ronald Reagan was to money.
-- The Unix Haters Handbook
