Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A Understanding semicolons in Bash functions

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 kn...

posted 1d ago by alx‭  ·  edited 1d ago by alx‭

Answer
#3: Post edited by user avatar alx‭ · 2025-01-21T00:13:47Z (1 day ago)
  • 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 by user avatar alx‭ · 2025-01-21T00:13:20Z (1 day ago)
  • 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 by user avatar alx‭ · 2025-01-21T00:13:09Z (1 day ago)
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.