forked from extern/nushell
a7c1b363eb
# Description The previous behaviour broke for me because I didn't have `sh` in my path for my nu script. I think we shouldn't assume that just because a file ends with `.sh` it should be executed with `sh`. `sh` might not be available or the script might contain a hashbang for a different shell. The idea with this PR is that nushell shouldn't assume anything about executable files and just execute them. Later on we can think about how non-executable files should be executed if we detect they are a script. # User-Facing Changes This may break some people's scripts or habits if they have wrong assumptions about `.sh` files. We can tell them to add a hashbang and +x bit to execute shell scripts, or prepend `bash`. If this a common assumption something like this should be added to the book # Tests + Formatting I only tested manually and that did work # After Submitting Co-authored-by: Jelle Besseling <jelle@bigbridge.nl> |
||
|---|---|---|
| .. | ||
| assets | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| LICENSE | ||