From: Jeff Squyres; Tuesday, March 09, 2004 12:19 PM > On Tue, 9 Mar 2004, Lombard, David N wrote: > > > > Now this is surprising to me. I would not expect the last line by > > looking at what you did. > > This is how switcher has *always* been -- the switcher command only > changes your preferences, it does *not* change your current environment. > It is very strongly documented this way. From the text:
I understand this is what it's always done -- I expected that. I've never used switcher, given my LAM preference. :^D > In fact, it would be very difficult to make it change your current > environment -- there's a bunch of very sitcky technical issues involved. The Unicos modules command worked that way (changing the current environment), similarly to my understanding of the underlying modules project, by aliasing commands to source directly into the current shell. This is what switch-reload does, change the current environment, correct? > > > > $ switcher-reload > > > $ which mpirun > > > /opt/mpich-1.2.3/bin/mpirun > > > > The $(switcher-reload) step should have been executed by the first > > switcher command above to honor the "principle of least surprise." I'm > > not aware of any similar "commit" processing at the command line. > > It would be really, really hard to do this. OK. I'm not trying to suddenly force any changes -- I'm happy to drop this thread. -- David N. Lombard My comments represent my opinions, not those of Intel Corporation. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
