Post History
The shell uses ; to reliably end a statement, with foreground execution. In some cases, a line break also ends a statement with foreground (except that when the statement is not obviously complete...
Answer
#5: Post edited
The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is not obviously complete, a line break does not end it). (I don't know if "statement" is the technical term.)- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
- The shell uses `;` to reliably end a statement, with foreground execution. In some cases, a line break also ends a statement with foreground (except that when the statement is not obviously complete, a line break does not end it). (I don't know if "statement" is the technical term.)
- When you want to end a statement, and execute it in the foreground, use `&` instead of `;`.
- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
#4: Post edited
The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). (I don't know if "statement" is the technical term.)- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
- The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is not obviously complete, a line break does not end it). (I don't know if "statement" is the technical term.)
- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
#3: Post edited
The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). I don't know if statement is the technical term.- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
- The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). (I don't know if "statement" is the technical term.)
- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
#2: Post edited
bash(1) uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). I don't know if statement is the technical term.- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
- The shell uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). I don't know if statement is the technical term.
- I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.
#1: Initial revision
bash(1) uses `;` to reliably end a statement. In some cases, a line break also ends a statement (except that when the statement is obviously incomplete, a line break does not end it). I don't know if statement is the technical term. I personally always use `;` as if I were writing C code, unless running some one-liner interactively. IMO, the semicolons add readability.