You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clearly separate quarantine variable definition from tclsh binary on
modulecmd.tcl evaluated command call in _module_raw function for sh,
bash, ksh and zsh shells.
When _module_raw is evaluted in zsh completion process, the command call
was not correctly generated and location of tclsh binary was the value
set to all quarantine variable declared. Which in case of LD_PRELOAD,
led to error messages.
Fixescea-hpc#350.
Clearly separate quarantine variable definition from tclsh binary on
modulecmd.tcl evaluated command call in _module_raw function for sh,
bash, ksh and zsh shells.
When _module_raw is evaluted in zsh completion process, the command call
was not correctly generated and location of tclsh binary was the value
set to all quarantine variable declared. Which in case of LD_PRELOAD,
led to error messages.
Fixescea-hpc#350.
Clearly separate quarantine variable definition from tclsh binary on
modulecmd.tcl evaluated command call in _module_raw function for sh,
bash, ksh and zsh shells.
When _module_raw is evaluted in zsh completion process, the command call
was not correctly generated and location of tclsh binary was the value
set to all quarantine variable declared. Which in case of LD_PRELOAD,
led to error messages.
Fixescea-hpc#350.
When some environment variables are defined for Modules quarantine mechanism:
Completion script on Zsh shell returns inconsistent results:
It seems related to the evaluation of following line in
_module_raw
shell function:Quarantine variables set in
_mlre
variable are expanded to the/usr/bin/tclsh
value rather being set empty.The text was updated successfully, but these errors were encountered: