-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for zsh #702
Comments
@Flamefire Full support for Very recently (see #667) we have included a module file to initialize your environment for using EESSI, so you can now also do this:
The benefit here is that this should work across different types of shells (anything that Lmod supports), and that it's reversible ( There are some known issues though, see for example #694 |
This is in the works, as of last week you can use EESSI as a module. Assuming you already have Lmod available
We are working towards including best practices (i.e., implementing an Lmod family for local and EESSI software stacks so you don't accidentally mix them...which may or may not work depending on what you try to do). |
@Flamefire BTW, a better channel to ask for help is the EESSI support portal , see https://www.eessi.io/docs/support |
If Lmod is not available, as of last night this is now in place via
|
Again, this is very new and will probably subject to some tweaking over the next few weeks |
Closing this as done |
Currently there is only an
init/bash
script which doesn't work on e.g.zsh
for obvious reasons.Is the requirement of a bash shell documented already? Can other shells (as far as they are supported by lmod) also be supported?
Our users just asked about zsh in particular
The text was updated successfully, but these errors were encountered: