-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
MobaXterm or GitBash? #20
Comments
fully on board with at least adding gitbash. I wouldn't drop MobaXterm as it appears to have some nice features. |
MobaXterm does have some nice features. We don't use them, but still. Thing to do it likely add Git Bash and also a quick summarizing table of why/when people might want to choose one over the other. |
Regardless of the choice, I would pick just one to use throughout the lesson. Presenting multiple options will ultimately distract from the intent of teaching new users the basics of logging into an HPC system. An instructor could say something along the lines of: "There are multiple options, and if you find your needs outgrow the tools we are discussing today, please contact us." |
+1 to @pdoehle's suggestion |
The shell-novice lesson has a rather good overview of terminal applications for the three OSes. Git for Windows (umbrella project including I'm afraid Cygwin is becoming passé, since Microsoft has begun committing to open source toolchains. What a time to be alive! |
Yeah, let’s recommend git-bash. Putty, WSL and mobaxterm deserve honorable mention as good alternative options. |
Oh good, already committed language to this effect in an upcoming PR :-) |
The current version of the login suggests that MobaXterm is used on Windows (or PuTTY). This certainly gets the job done. However, Software Carpentry uses GitBash. I know that the reason for MobaXterm is at least partly historical (it had nano while GitBash didn't and so was adopted by Compute Canada) and now not relevant (Oliver Stueker added nano to GitBash).
Would GitBash be a better option here so that:
?
The text was updated successfully, but these errors were encountered: