Users
Search
Help
Sign Up
Sign In
Communities
Writing
Codidact Meta
The Great Outdoors
Photography & Video
Scientific Speculation
Cooking
Electrical Engineering
Judaism
Languages & Linguistics
Software Development
Mathematics
Christianity
Code Golf
Music
Physics
Linux Systems
Power Users
Tabletop RPGs
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 »
Users
Search
Help
Dashboard
Sign In
Sign Up
Q&A
Meta
Review Suggested Edit
You can't approve or reject suggested edits because you haven't yet earned the
Edit Posts
ability.
View post
Pending.
This suggested edit is pending review.
Suggested edit summary:
78 / 255
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
fore
ground, 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.
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
back
ground, 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.
Suggested
4 days ago
by
bgstack15