Eugeen Sablin 9e1e2a4320 provide env to commands and try to start provided path (#10302) ... fixes #8551 # Description Use `open::commands` function to get list of command available for starting given path. run commands directly, providing environment, until one of them is successful. example of output if start was not successful: ``` ~\code\nushell> start ..\nustart\a.myext 09/12/2023 01:37:55 PM Error: nu:🐚:external_command × External command failed ╭─[entry #1:1:1] 1 │ start ..\nustart\a.myext · ─────────┬──────── · ╰── No command found to start with this path ╰──── help: Try different path or install appropriate command Command `cmd /c start "" "..\nustart\a.myext"` failed with exit code: 1 ``` # User-Facing Changes `start` command now provides environment to the external command. This is how it worked in `nu 0.72`, see linked issue. # Tests + Formatting `start` command didn't have any tests and this PR does not add any. Integration-level tests will require setup specific to OS and potentially change global environment on testing machine. For unit-level test it is possible to test `try_commands` function. But is still runs external commands, and robust test will require apriori knowledge which commands are necessary successful to run and which are not.		2023-09-12 14:03:41 +02:00
..
src	provide env to commands and try to start provided path (#10302)	2023-09-12 14:03:41 +02:00
tests	Rename random decimal to random float (#10320)	2023-09-12 13:03:05 +02:00
Cargo.toml	Bump calamine and fix clippy (#10314)	2023-09-11 12:39:52 +02:00
LICENSE	Fix rest of license year ranges (#8727)	2023-04-04 09:03:29 +12:00