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
Windows PowerShell has been included by default since Windows 10 version 1607, and it has less friction with bash syntax than CMD, for instance:
It supports the use of a forward slash / in paths, as well as the ./ notation.
It allows the execution of .exe files without requiring the file extension (e.g., main can be used in place of main.exe, which is also supported by CMD).
It supports the use of single quotes for defining literal strings.
I’m willing to contribute if you agree with this.
The text was updated successfully, but these errors were encountered:
Windows PowerShell has been included by default since Windows 10 version 1607, and it has less friction with bash syntax than CMD, for instance:
/
in paths, as well as the./
notation.main
can be used in place ofmain.exe
, which is also supported by CMD).I’m willing to contribute if you agree with this.
The text was updated successfully, but these errors were encountered: