Closed helmutcarter closed 9 months ago
Hello Helmut,
What you observe is the expected behavior of modulecmd
command.
Modules tool is based on two components:
modulecmd
script that evaluates modulefiles and output their environment change settings on stdoutmodule
shell function that takes modulecmd
output and evaluates it in the current shell session to update itSo you need to use the module
shell function from your shell session, not the modulecmd
script.
There is a fish initialization script provided with Modules that defines the module
shell function. Given the information you provided, you should find this script at /cm/local/apps/environment-modules/4.5.3/init/fish
.
$ source /cm/local/apps/environment-modules/4.5.3/init/fish
Regards, Xavier
Hello Xavier,
Thank you for clearing that up. For some reason my fish shell had been set to automatically expand 'module' into 'modulecmd fish', so I assumed modulecmd was what I should be using.
Warmly, Helmut
Describe the bug
When I try to load a module in fish, it ostensibly print the commands it should run to stdout.
To Reproduce
Steps to reproduce the behavior:
Location and content of any modulerc or modulefile involved:
Expected behavior
I expect the python2 module to be loaded. I have no issue when I do this in bash. This also happens with other module files in fish for me.
Error and debugging information
Modules version and configuration
Additional context
None. Thank you!