nushell

mirror of https://github.com/nushell/nushell.git synced 2025-06-02 16:16:01 +02:00

History

fix: implicitly running .ps1 scripts with spaces in path (#15781 )

- this PR should close #15757

# Description

> [!NOTE]
> [`-File <filePath>
<args>`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1#-file----filepath-args)
> - Enter the script filepath and any parameters
> - All values typed after the File parameter are interpreted as the
script filepath and parameters passed to that script.

> [!NOTE]
>
[`-Command`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_powershell_exe?view=powershell-5.1#-command)
> - The value of Command can be -, a _script block_, or a _string_.
> - In `cmd.exe` (and other externall callers), there is no such thing
as a _script block_, so the value passed to Command is always a
_**string**_.
> - A string passed to Command is still executed as PowerShell code.

> [!NOTE]
> [Call operator
`&`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_operators?view=powershell-5.1#call-operator-)
> - Runs a command, ***script***, or script block.

Basically using `-Command` to run scripts would require _another_ layer
of quoting and escaping. It looks like `-File` is the way to run
powershell scripts as an external caller.

# User-Facing Changes

# Tests + Formatting

# After Submitting

Co-authored-by: Bahex <17417311+Bahex@users.noreply.github.com>

2025-05-21 14:47:26 -05:00

src

fix: implicitly running .ps1 scripts with spaces in path (#15781 )

2025-05-21 14:47:26 -05:00

tests

fix: implicitly running .ps1 scripts with spaces in path (#15781 )

2025-05-21 14:47:26 -05:00

Cargo.toml

Rust 1.85, edition=2024 (#15741 )

2025-05-13 16:49:30 +02:00

LICENSE

Fix rest of license year ranges (#8727 )