Massimo Marino writes:
[snip]
> in the PATH /usr/bin was coming before /sw/bin . Fixing that
> (source init.sh in .bash_profile) rather than into .bashrc got
> the PATH right. I still do not have an answer on WHY which
> emacs was reporting /sw/bin/emacs.
>
> I had this problem after moving from csh to bash. Is any bash
> expert able to explain the 'which' bug/feature?
Well, in csh, 'which' is a shell builtin: in bash, it is
not. This might have some effect; with the builtin 'which', a new
shell process would not get invoked, whereas in bash it would be.
It could be that your PATH is somehow getting munged in the
process, depending on how you set up your environment in the
first place.
You could test this by writing a simple wrapper script like this:
#!/bin/bash
echo $PATH
/sw/bin/which $*
and calling it 'mywhich' and invoking that to see what happens to
the PATH.
Seems unlikely, though...
--
V.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
