03:33 pm, 4 Nov 03
teach me something about unix
Can someone explain why this isn't doing what I expect? (This isn't a trick question; I'm honestly confused.)
Why is it running the old one?
For context:
And even weirder, if I try to strace it, it runs the right one. Eh?
Update: "rehash" is the csh/zsh command to rehash path lookups, while "hash" is the command used by bash (which I wasn't aware of).
~$ /usr/bin/mutt -v | head -1 Mutt 1.3.28i (2002-03-13) ~$ /home/martine/local/bin/mutt -v | head -1 Mutt 1.4.1i (2003-03-19) ~$ which mutt /home/martine/local/bin/mutt ~$ mutt -v | head -1 Mutt 1.3.28i (2002-03-13)
Why is it running the old one?
For context:
~$ alias alias ls='ls --color=auto' ~$ rehash bash: rehash: command not found ~$ echo $PATH /home/martine/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
And even weirder, if I try to strace it, it runs the right one. Eh?
Update: "rehash" is the csh/zsh command to rehash path lookups, while "hash" is the command used by bash (which I wasn't aware of).
And I'm using Slackware, which suggests that it's not a matter of distribution.
i see that quite often.
How would you like to give a zsh talk to the lug? I've never used it, don't know anything about it, but have heard cool things about it. I imagine others are the same. Also, I need your name in blood and a copy of your student ID.
In bash and family, use :
% which pwd /bin/pwd % type pwd pwd () { local target=$(abs $*); if [ -f $target ]; then echo $(dirname $target); else echo $target; fi }And evan: use to rehash bash (it doesn't really rehash, it just clears the whole cache), not . Type to find out more.
on top of that, because lj by default adds linebreaks (though it doesn't within a p block, when you write
you get vertical whitespace between the end of the pre block and the following html (from the browser's settings for how pre should look) and then there are *two* brs (one for the \n immediately following the /pre, and then another for the blank line immediately following it) so you get a bit pile of white space. (see also the big chunk of whitespace following the blockquote because i put this paragraph on a new line, which means an extra br is inserted...)
sucks, i know. hard to think of a good solution. :\
and a lot of people now depend on the behavior so we can't change it.
really, the clients ought to always send html, and we ought to be able to post comments with a client, but...
Use something like <tt> for inline words, or to appease the W3C something like <span style="font-family: monospace">...</span> :)