[Modules] broken autoinit in modulecmd.tcl?
Manage your shell environment variables and aliases
Brought to you by:
xdelaruelle
From: Thomas Z. <tho...@rr...> - 2006-11-23 09:09:10
|
Dear all, I'm not sure if I'm doing something completely wrong or if the "autoinit" initialisation of the modulecmd.tcl is really broken: According to the CVS history, the first lines of modulecmd.tcl (#!...) which detected where tclsh could be found and executed were removed with commit 1.75. If I initialize modules with . /some-path/init/bash I get module () eval `$TCLSH /some-path/modulecmd.tcl bash $*` which is fine as $TCLSH is set to the autodetected tclsh binary and modulecmd.tcl is given as argument. If I however do eval `/some-path/modulecmd.tcl bash autoinit` which I expected to be the "news style of doing", I get module () eval `'/some-path/modulecmd.tcl' 'bash' $*` which is exactly what is coded in the autoinit function of modulecmd.tcl but using this newly defined alias/shell function fails because modulecmd.tcl cannot be executed as command (the shell does not know what type of script it is as there is no #!... at the beginning of the file) Regards, thomas -- Dipl.-Ing. Thomas ZEISER Regionales Rechenzentrum Erlangen Martensstr. 1, 91058 Erlangen, GERMANY |