From 7a95d7c36dc664f62716f65d32a258dfdd0e39b0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20=C5=BD=C3=A1dn=C3=ADk?= Date: Mon, 3 Jun 2024 22:05:20 +0300 Subject: [PATCH 1/4] Add 0.94.2 patch notes --- blog/2024-06-03-nushell_0_94_2.md | 63 +++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 blog/2024-06-03-nushell_0_94_2.md diff --git a/blog/2024-06-03-nushell_0_94_2.md b/blog/2024-06-03-nushell_0_94_2.md new file mode 100644 index 0000000000..19f065f1c7 --- /dev/null +++ b/blog/2024-06-03-nushell_0_94_2.md @@ -0,0 +1,63 @@ +--- +title: Nushell 0.94.2 +author: The Nu Authors +author_site: https://twitter.com/nu_shell +author_image: https://www.nushell.sh/blog/images/nu_logo.png +excerpt: Today, we're releasing version 0.94.2 of Nu. This is a patch release to fix issues introduced by 0.94.0 and 0.94.1. +--- + +# Nushell 0.94.2 + +Nushell, or Nu for short, is a new shell that takes a modern, structured approach to your command line. It works seamlessly with the data from your filesystem, operating system, and a growing number of file formats to make it easy to build powerful command line pipelines. + +Today, we're releasing version 0.94.2 of Nu. This is a patch release to fix issues introduced by 0.94.0 and 0.94.1, namely backslash expansions of external commands and paths handling in globs. + +# Where to get it + +Nu 0.94.2 is available as [pre-built binaries](https://github.com/nushell/nushell/releases/tag/0.94.2) or from [crates.io](https://crates.io/crates/nu). If you have Rust installed you can install it using `cargo install nu`. + +As part of this release, we also publish a set of optional plugins you can install and use with Nu. To install, use `cargo install nu_plugin_`. + +# Table of content + +- [Nushell 0.94.2](#nushell-0942) +- [Where to get it](#where-to-get-it) +- [Table of content](#table-of-content) +- [Highlights and themes of this release \[toc\]](#highlights-and-themes-of-this-release-toc) + - [Fix external command name parsing with backslashes \[toc\]](#fix-external-command-name-parsing-with-backslashes-toc) + - [Preserving absolute paths when expanding globs \[toc\]](#preserving-absolute-paths-when-expanding-globs-toc) + - [Known Bug #13020 \[toc\]](#known-bug-13020-toc) +- [Full changelog \[toc\]](#full-changelog-toc) + +# Highlights and themes of this release [[toc](#table-of-content)] + +This hotfix contains two fixes: + +## Fix external command name parsing with backslashes [[toc](#table-of-content)] + +https://github.com/nushell/nushell/pull/13027 + +After the last release, external commands on Windows would incorrectly interpret backslashes as escape sequences despite being unquoted, for example: +``` +alias curl = c:\msys64\clangarm64\bin\curl.exe + ───────────────┬────────────── + ╰── unrecognized escape after '\' in string +``` + +This is now fixed by [#13027](https://github.com/nushell/nushell/pull/13027) and externals should work correctly. + +## Preserving absolute paths when expanding globs [[toc](#table-of-content)] + +[#13028](https://github.com/nushell/nushell/pull/13028) fixes a bug when an unquoted tilde wasn't expanded properly to the home directory. + +## Known Bug [#13020](https://github.com/nushell/nushell/issues/13020) [[toc](#table-of-content)] + +Currently, we have one more known regression after 0.94.0, where attempting to run a PowerShell script on Windows using `.\script.ps1` would result in an error instead of opening an editor with the said file (or running the script). We are still looking into this one, but it seems more tricky to resolved, so we decided to release at least the two above bugfixes. + +The workaround for this problem is to spawn the file with PowerShell manually, such as `pwsh -f script.ps1` or `powershell.exe -f script.ps1`. + +# Full changelog [[toc](#table-of-content)] + +- [devyn](https://github.com/devyn) created + - [Fix external command name parsing with backslashes, and add tests](https://github.com/nushell/nushell/pull/13027) + - [Fix run_external::expand_glob() to return paths that are PWD-relative but reflect the original intent](https://github.com/nushell/nushell/pull/13028) From e48f49b5833e4e4ac7f9a0069fdf5564e98878e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20=C5=BD=C3=A1dn=C3=ADk?= Date: Mon, 3 Jun 2024 22:29:41 +0300 Subject: [PATCH 2/4] Reword --- blog/2024-06-03-nushell_0_94_2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2024-06-03-nushell_0_94_2.md b/blog/2024-06-03-nushell_0_94_2.md index 19f065f1c7..f50d341dc7 100644 --- a/blog/2024-06-03-nushell_0_94_2.md +++ b/blog/2024-06-03-nushell_0_94_2.md @@ -31,7 +31,7 @@ As part of this release, we also publish a set of optional plugins you can insta # Highlights and themes of this release [[toc](#table-of-content)] -This hotfix contains two fixes: +This patch release contains two fixes: ## Fix external command name parsing with backslashes [[toc](#table-of-content)] From 38bd5c8c2eda5e1aa5ef4dced4480535afcc7622 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20=C5=BD=C3=A1dn=C3=ADk?= Date: Mon, 3 Jun 2024 22:29:57 +0300 Subject: [PATCH 3/4] Remove link --- blog/2024-06-03-nushell_0_94_2.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/blog/2024-06-03-nushell_0_94_2.md b/blog/2024-06-03-nushell_0_94_2.md index f50d341dc7..4a13dcce5d 100644 --- a/blog/2024-06-03-nushell_0_94_2.md +++ b/blog/2024-06-03-nushell_0_94_2.md @@ -35,8 +35,6 @@ This patch release contains two fixes: ## Fix external command name parsing with backslashes [[toc](#table-of-content)] -https://github.com/nushell/nushell/pull/13027 - After the last release, external commands on Windows would incorrectly interpret backslashes as escape sequences despite being unquoted, for example: ``` alias curl = c:\msys64\clangarm64\bin\curl.exe From 4a817a8d3277766d2e765a249711e609581951b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20=C5=BD=C3=A1dn=C3=ADk?= Date: Mon, 3 Jun 2024 22:34:49 +0300 Subject: [PATCH 4/4] Reword --- blog/2024-06-03-nushell_0_94_2.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/blog/2024-06-03-nushell_0_94_2.md b/blog/2024-06-03-nushell_0_94_2.md index 4a13dcce5d..2531424092 100644 --- a/blog/2024-06-03-nushell_0_94_2.md +++ b/blog/2024-06-03-nushell_0_94_2.md @@ -35,7 +35,7 @@ This patch release contains two fixes: ## Fix external command name parsing with backslashes [[toc](#table-of-content)] -After the last release, external commands on Windows would incorrectly interpret backslashes as escape sequences despite being unquoted, for example: +After the last release, external commands on Windows would incorrectly interpret backslashes in their path as escape sequences despite being unquoted, for example: ``` alias curl = c:\msys64\clangarm64\bin\curl.exe ───────────────┬────────────── @@ -46,11 +46,11 @@ This is now fixed by [#13027](https://github.com/nushell/nushell/pull/13027) and ## Preserving absolute paths when expanding globs [[toc](#table-of-content)] -[#13028](https://github.com/nushell/nushell/pull/13028) fixes a bug when an unquoted tilde wasn't expanded properly to the home directory. +[#13028](https://github.com/nushell/nushell/pull/13028) fixes a bug when an unquoted tilde wasn't expanded properly to the home directory when being a subject of globbing. ## Known Bug [#13020](https://github.com/nushell/nushell/issues/13020) [[toc](#table-of-content)] -Currently, we have one more known regression after 0.94.0, where attempting to run a PowerShell script on Windows using `.\script.ps1` would result in an error instead of opening an editor with the said file (or running the script). We are still looking into this one, but it seems more tricky to resolved, so we decided to release at least the two above bugfixes. +Currently, we have one more known regression after 0.94.0, where attempting to run a PowerShell script on Windows using `.\script.ps1` would result in an error instead of opening an editor with the said file or running the script. We are still looking into this one, but it seems more tricky to resolve, so we decided to release at least the above two bugfixes. The workaround for this problem is to spawn the file with PowerShell manually, such as `pwsh -f script.ps1` or `powershell.exe -f script.ps1`.