3 ms·
You don't need the backslashes in that case. As with lines ending in pipes and a few other places, the line continuation is implicit after the &&: https://unix
by js2 2y ago
You don't need the backslashes in that case. As with lines ending in pipes and a few other places, the line continuation is implicit after the &&:
https://unix.stackexchange.com/questions/253518/where-are-bash-line-continuations-after-and-documented https://unix.stackexchange.com/questions/253518/where-are-ba...
- yjftsjthsd-h 2y agoHuh, neat. So I picked that habit up from writing Dockerfiles, which does let you do RUN foo && \ bar && \ : but not RUN foo && bar && : (I just tested it), but more recently you can just write RUN <<EOF foo bar EOF so with the caveat of needing to `set -e` the whole thing might be a moot point now:)