On 2013-12-05 12:27-0500 Matthew Woehlke wrote:
On 2013-12-05 02:36, Alan W. Irwin wrote:
Sorry, this turned out to be a false alarm. Despite "which cmake"
telling me I was using cmake-2.8.12.1 [snip]
...which is, of course, why you should always use "type" in bash rather than
"which" :-). "type", being a shell built-in, will tell you what bash will
*actually* run, hashing - and shell builtins, and functions, and aliases -
included.
Hi Matthew:
Thanks for that really good tip; the "type" bash builtin is a
bash-aware replacement for "which" that would have allowed me to completely
avoid
this false alarm.
My problem is I stuck with tcsh much too long (15 years of experience
until 2003 or so when someone I knew finally convinced me to switch to
bash). I have really liked bash ever since, but I still have some
command-line habits left from my tcsh days which almost always work
(like using "which") so I am unaware of those habits and therefore
don't look hard enough for alternatives. But due to this bad
experience with a stale cache I will definitely switch from "which" to
"type" from now on.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
