You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have set shell := ["pwsh", "-c"] # PowerShell 7.3.2 Core (Multi-Platform) I get
echo ': test'
: test
cmdlet Write-Output at command pipeline position 1
Supply values for the following parameters:
InputObject:
If I hit Ctrl+C then InputObject: ends up InputObject: error: Recipe `test` failed on line 14 with exit code 1
echo ': test'
: test
cmdlet Write-Output at command pipeline position 1
Supply values for the following parameters:
InputObject: error: Recipe `test` failed on line 14 with exit code 1
I've had PowerShell Core installed for about a year now and never experienced this issue before.
If I use set positional-arguments I get
echo ': test'
: test
test
Which is adding the name of the recipe test as an additional argument on each line which I believe hides the InputObject error. As this doesn't happen when using the default shell I'm inclined to believe this is a change in PowerShell which I believe updated recently. But not 100% sure and wanted to point out the problem.
The text was updated successfully, but these errors were encountered:
I've not tested this on Windows yet and wondering if any windows users are experiencing this with Just 1.13.0 using PowerShell Desktop and PowerShell Core.
On macOS Big Sur 11.7.3 with the recipe
If I have
set shell := ["pwsh", "-c"] # PowerShell 7.3.2 Core (Multi-Platform)
I getIf I hit
Ctrl+C
thenInputObject:
ends upInputObject: error: Recipe `test` failed on line 14 with exit code 1
I've had PowerShell Core installed for about a year now and never experienced this issue before.
If I use
set positional-arguments
I getWhich is adding the name of the recipe
test
as an additional argument on each line which I believe hides theInputObject
error. As this doesn't happen when using the default shell I'm inclined to believe this is a change in PowerShell which I believe updated recently. But not 100% sure and wanted to point out the problem.The text was updated successfully, but these errors were encountered: