Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add 0.94.2 patch notes #1436

Merged
merged 4 commits into from
Jun 3, 2024
Merged

Add 0.94.2 patch notes #1436

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7a95d7c
Add 0.94.2 patch notes
kubouch Jun 3, 2024
e48f49b
Reword
kubouch Jun 3, 2024
38bd5c8
Remove link
kubouch Jun 3, 2024
4a817a8
Reword
kubouch Jun 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Reword
  • Loading branch information
@kubouch
kubouch committed Jun 3, 2024
commit 4a817a8d3277766d2e765a249711e609581951b7
6 changes: 3 additions & 3 deletions blog/2024-06-03-nushell_0_94_2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
───────────────┬──────────────
Expand All @@ -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`.

Expand Down