Amin Yahyaabadi 260ff99710
feat: spawn the executables directly if possible (#3974)
* feat: spawn the executables directly if possible

This pull request changes nu-command so that it spawns the process directly if:
- They are a `.exe` on Windows
- They are not a `.sh` or `.bash` on not windows.

Benefits:
- As I explained in [this comment](https://github.com/nushell/nushell/issues/3898#issuecomment-894000812), this is another step towards making Nushell a standalone shell, that doesn't need to shell out unless it is running a script for a particular shell (cmd, sh, ps1, etc.).
- Fixes the bug with multiline strings
- Better performance due to direct spawning.

For example, this script shows ~20 ms less latency.
After:
```nu
C:\> benchmark { node -e 'console.log("sssss")' }
───┬──────────────────
 # │    real time
───┼──────────────────
 0 │ 63ms 921us 600ns
───┴──────────────────
```
Before
```nu
C:\> benchmark { node -e 'console.log("sssss")' }
───┬──────────────────
 # │    real time
───┼──────────────────
 0 │ 79ms 136us 800ns
───┴──────────────────
```

Fixes #3898

* fix: make which dependency optional

Also fixes clippy warnings

* refactor: refactor spawn_exe, spawn_cmd, spawn_sh, and spawn_any

* fix: use which feature instead of which-support

* fix: use which_in to use the cwd of nu

* fix: use case insensitive comparison of the extensions

Sometimes the case of the extension is uppercased by the "which_in" function

Also use unix instead of not windows. Some os might not have sh support
2021-09-01 09:38:52 -05:00
..
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-28 15:59:09 +03:00
2021-08-28 15:59:09 +03:00
2021-08-27 20:48:58 +12:00
2021-08-28 15:59:09 +03:00
2021-08-28 15:59:09 +03:00
2021-08-28 15:59:09 +03:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00
2021-08-27 20:48:58 +12:00

Nushell core libraries and plugins

These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.

Foundational libraries are split into two kinds of crates:

  • Core crates - those crates that work together to build the Nushell language engine
  • Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.

Plugins are likewise also split into two types:

  • Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
  • Extra plugins - these plugins run a wide range of differnt capabilities like working with different file types, charting, viewing binary data, and more.