yes continue
Answer from Reno on Stack Overflowcsh - continue in unix - Stack Overflow
shell - In a Bash Script how does the continue command work with embedded loops? - Unix & Linux Stack Exchange
bash - Return "continue" from function called from loop - Unix & Linux Stack Exchange
shell script - when to use line-continuation character and when not? - Unix & Linux Stack Exchange
Can I use `break` and `continue` in the same loop?
Can I use `break` and `continue` outside a loop?
Do `break` and `continue` work in `select` loops?
Videos
You can use 'return` with a parameter for example like the following,
#!/bin/bash
AFunction () {
if [[ "${RED}" -lt 3 ]]; then
echo "cont"
return 1
else
echo "nope"
return 0
fi
}
for i in 1 2 3 4 5
do
RED=${i}
if AFunction
then
echo ${i}
fi
done
#!/bin/sh
AFunction () {
[ "${RED}" -lt 3 ]
}
for i in 1 2 3 4 5
do
RED=${i}
if AFunction
then
echo "cont"
else
echo "nope"
echo ${i}
fi
done
The simple answer is that because the former needs it, and the latter doesn't.
That find command is a single simple shell command, which just takes a number of distinct arguments, and has a structure of its own. Those arguments are just not meaningful to the shell, so it doesn't know there's e.g. a logical connection between the ( and the ). The whole command could be written on a single line, it would just be harder to read.
Without the line continuations, find would run on playground with the default printing action, and then the shell would try to run the command ( without arguments (or, the command -type in a subshell, if you were to remove the escape from the (, too):
find playground
\(
-type f
...
On the other hand, the if compound statement is part of the shell syntax, and the shell knows what parts there are to expect. After the then there must be a command, and eventually an else or fi. The whole structure could also be written on a single line, but then we'd need to add semicolons before the else and the fi. (In the same way echo foo; echo bar requires to semicolon or a newline to be taken as two commands.)
This is a particularly complex example because some of the \ there are what you're calling "line-continuation" but others are to protect characters so the shell doesn't interpret them and instead passes them to find. Specifically, the \(, \) and \; are there so that the shell doesn't interpret the escaped characters and passes them as-is to find. The rest, the \ that aren't immediately before a non-space character are line continuation signals.
In general, if you want to break a command, you need the \ unless you break on one of the "list terminator" characters. So, if you cut after one of these, you don't need the \:
; & && || | |& ;;
For example, echo foo && echo bar can be written as:
echo foo &&
echo bar
No need for \. Alternatively, the same thing can also be written as:
echo \
foo \
&&
echo \
bar
Note how I have used the \ when cutting at places that are neither the end of a command nor a list terminator.
If you cut a command anywhere else, you need the \. You don't need the \ in the if ... then ... else ... example you show because there, you aren't cutting a command. Each command is on its own line, and that's fine. You only need the \ if you want to break a single command onto multiple lines.
As @paul_pedant correctly pointed out in the comments, you can make the command much clearer if you use single quotes to escape things for find:
find playground \
'(' \
-type f \
-not -perm 0600 \
-exec chmod 0600 {} ';' \
')' \
-or \
'('
other options...
')'