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
{{ message }}
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.
As was mentioned in issue #22, there are some problems with PuTTY.
Specifically, although it is a great tool for Windows users to access a remote Unix server, it does not have the ability to act in a Unix-like way on a user's local Windows PC.
This issue is to act as a placeholder to discuss this. Should we recommend PuTTY or something(s) else?
The text was updated successfully, but these errors were encountered:
I think we should recommend using Git for Windows, since it's a full-featured terminal already used in the Software Carpentries workshops. PuTTY is an excellent small utility, but bash provides users/learners with a lot more flexibility.
Agreed, I think keeping the ties to other carpentry material is a good idea. Let’s stick with the recommendations of shell-novice as they don’t compromise our material in any way.
I'm not sure if this is just for Windows 10 though. Similarly there are more flavours in the Windows App Store, but again I'm not sure which versions of Windows can use them.
As was mentioned in issue #22, there are some problems with PuTTY.
Specifically, although it is a great tool for Windows users to access a remote Unix server, it does not have the ability to act in a Unix-like way on a user's local Windows PC.
This issue is to act as a placeholder to discuss this. Should we recommend PuTTY or something(s) else?
The text was updated successfully, but these errors were encountered: