Reputation
935
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 9 25
Newest
 Custodian
Impact
~221k people reached

Jan
31
awarded  Custodian
Jan
31
reviewed No Action Needed Rsyslog not creating dynamic directories
Jan
21
revised Catch “command not found” from shell script
realized that "file" was missing in $_executables
Jan
21
answered Catch “command not found” from shell script
Jan
9
comment Where are bash line continuations after && and || documented?
As you found, ending lines with && and || is not well documented and thus uncommon (except in your shop apparently). On seeing the example, my first thought was "syntax error". I've been writing shell script for decades and still had to look it up and run it to prove it is correct. Lines ending in '&' (run in background) are more common to me (and erroneous key repeats as well). Though this example works, using multiple && and || clauses is highly unreliable due to how they differ from the expected if-then logic. The epllipsis in english means "more to follow" so that makes more sense to me.
Jan
8
comment Where are bash line continuations after && and || documented?
I wish bash supported an ellipsis (...) for line continuation. It would prevent a lot of logic bugs. But we can't have everything.
Dec
24
awarded  Necromancer
Nov
18
awarded  Yearling
Nov
17
awarded  Popular Question
Oct
14
awarded  Nice Question
Sep
14
awarded  Necromancer
Aug
3
awarded  Nice Question
Jul
31
revised What does env x='() { :;}; command' bash do and why is it insecure?
added emphasis and command list verbiage
Jul
31
answered What does env x='() { :;}; command' bash do and why is it insecure?
Jul
11
answered Differentiating between running and being sourced in a bash shell script?
Jun
1
awarded  Custodian
Jun
1
awarded  Citizen Patrol
May
27
awarded  Nice Answer
May
21
reviewed Reject Recovering from 'grub rescue>' crash
Apr
19
awarded  Excavator