Re: IceWM-user Digest, Vol 38, Issue 1
"Walter Dnes" <[email protected]>
| Newsgroups | gmane.comp.window-managers.icewm.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Mar 08, 2010 at 02:58:19PM +0000, Anthony Campbell wrote > Thanks to everyone who replied to this thread. I found the problem in > the end: I had a file in $HOME/bin called "which", containing the one > line "type -path". Deleting this made things work normally. I don't know > why it had this effect, especially since I have the same file on a > different machine where it doesn't produce this effect. Anyway, it's > fine now. "/usr/bin/which" is a posix utility that can find the first occurence of an executable file (script or compiled program) in your path; e.g. [d531][waltdnes][~] which firefox /usr/bin/firefox I will make a logical deduction here. On the machine which had problems, your PATH variable has $HOME/bin (or some version thereof) *BEFORE* /usr/bin. This is probably what caused the problem. Take a look at your bash init file where PATH is set. I recommend putting your own stuff at the end. If you *ABSOLUTELY MUST* override the order, don't use $HOME/bin, because that puts *EVERY* local script/compiled program in there ahead of $HOME/bin. Instead... - create a directory $HOME/priority - put your scripts that you want over-riding standard programs in there - put $HOME/priority at the front of your PATH -- Walter Dnes <[email protected]> ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev