From 9687baa478681b1ba997df70a706122ec2f153f5 Mon Sep 17 00:00:00 2001 From: Dylan Allbee Date: Wed, 14 Apr 2021 08:45:22 -0700 Subject: [PATCH] Correct fish shell usage documentation Fish shell uses `&|` for combined stderr and stdout piping, not `^|`. --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 32f59697..d34d126e 100644 --- a/README.md +++ b/README.md @@ -88,11 +88,10 @@ have this shortcut, so use the long form: go test -v 2>&1 | pp -**Fish**: It uses [^ for stderr -redirection](http://fishshell.com/docs/current/tutorial.html#tut_pipes_and_redirections) -so the shortcut is `^|`: +**Fish**: `&|` redirects stderr and stdout. It's an alias for `2>&1 |` +([fish piping](https://fishshell.com/docs/current/index.html#piping)): - go test -v ^|pp + go test -v &| pp **PowerShell**: [It has broken `2>&1` redirection](https://connect.microsoft.com/PowerShell/feedback/details/765551/in-powershell-v3-you-cant-redirect-stderr-to-stdout-without-generating-error-records). The workaround is to shell out to cmd.exe. :(