Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
#4194
fish version: fish, version 3.1.0
OS: Darwin serenity 19.3.0 Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64
Did not try fish without third-party customizations.
I have a script (.fish) which attempts to execute this line: git checkout master > /dev/null ^&1
Issue #4194, which is closed, indicates that I am using the correct syntax.
However I get this error
~/.config/fish/functions/git-clean-branches.fish (line 51): Expected a string, but instead found a '&' git checkout master > /dev/null ^&1
This script was unchanged, and started breaking today.
Thanks, John Schank
The text was updated successfully, but these errors were encountered:
Yes, I think that's broken.
As a workaround (and as recommended in future, as the ^ syntax will eventually be removed), you can use >/dev/null 2>&1.
^
>/dev/null 2>&1
Sorry, something went wrong.
Bisects to 35671dd.
13b470a
Readd ^&1 redirection
^&1
eea919f
This was lost in 35671dd. Even tho we plan to drop caret redirection, while it's there it should fully work. Fixes #6591. (cherry picked from commit 13b470a)
No branches or pull requests
#4194
fish version:
fish, version 3.1.0
OS:
Darwin serenity 19.3.0 Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 x86_64
Did not try fish without third-party customizations.
I have a script (.fish) which attempts to execute this line:
git checkout master > /dev/null ^&1
Issue #4194, which is closed, indicates that I am using the correct syntax.
However I get this error
~/.config/fish/functions/git-clean-branches.fish (line 51): Expected a string, but instead found a '&'
git checkout master > /dev/null ^&1
This script was unchanged, and started breaking today.
Thanks,
John Schank
The text was updated successfully, but these errors were encountered: