3 ms·
That's a bit different. The change only exposed that some scripts were already broken and worked by accident. Specifying that your script should be run with #!/
by viraptor 10y ago
That's a bit different. The change only exposed that some scripts were already broken and worked by accident. Specifying that your script should be run with #!/bin/sh and then using bash syntax is what broke them. It's a bit like naming your files something.c, writing the code in C++ and compiling with `cc` just because `cc` happened to be linked to `c++` on your system. It will work for you, but don't be surprised when you distribute the source and people have problems using it.
Scripts that used #!/bin/bash still worked, scripts that actually used only sh syntax and #!/bin/sh still worked.
- ygra 10y agoSo there is actually no difference at all on Windows, then. Batch files have .cmd or .bat extensions and will continue to be run by cmd.
- viraptor 10y agoThat's the difference - the extensions continue to work, but the gui link to the application changes. Essentially now people will open powershell instead of cmd without necessarily realising.