Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Running build target fails with fish shell
See original GitHub issueWith the default shell set to fish building targets from the BAZEL BUILD TARGETS tree does not work. The && characters that are used in the terminal command cd <package directory> && bazel build <target> are not valid in the fish shell. Fish uses the syntax cd <package directory>; and bazel build <target>.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Fish error while trying to run command on mac
The <(a_command) syntax is a bash'ism not supported by fish. In keeping with the fish preference for explicit commands rather than magic ...
Read more >fish-shell/fish-shell
I build fish from the latest master commit every morning. Something broke in the last 24 hours which is causing the build to...
Read more >fish - ArchWiki
Once installed, simply type fish to drop into the fish shell. ... are run as usual and fish runs on top of Bash...
Read more >Documentation
stderr writes the standard error (file descriptor 2) of the target program to output.stderr . Piping. The user can string together multiple commands...
Read more >The fish Shell - Mark Volkmann
To make fish the default shell so new terminal windows ... To conditionally execute a command only if the previous command failed, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Looked like when you create the terminal you can control what shell is used, but that seemed like it would be an issue for windows. I guess that could platform check and only set the shell to bash or non windows?
The next release should fix this; I tested it by installing
fishand making it the default shell for VS Code’s integrated terminal. Launching Bazel as a task eliminates the need for us to run the command ascd && bazel.