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

60%
+1 −0
Q&A The Good, the Bad, and the Semicolon

A semicolon is a complex beast: You don't use it when you want an idea to stand on its own. You use a full stop for that. You don't use it to tie two ideas closely together because if you did, yo...

posted 7y ago by Kevin‭  ·  last activity 5y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2019-12-30T17:15:28Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/32004
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T07:31:13Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/32004
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T07:31:13Z (about 5 years ago)
A semicolon is a complex beast:

- You don't use it when you want an idea to stand on its own. You use a full stop for that.
- You don't use it to tie two ideas closely together because if you did, you'd relate them with lighter punctuation like a comma.
- You use it to relate two ideas weakly; it strongly implies there's a relationship between the two conjoined ideas but leaves it to the reader to determine what that implied relationship is.

As a result, it's difficult to use semicolons frequently without also using a slightly opaque writing style. When you use a semicolon, the fact that it clearly relates two clauses together without giving a direct indication what the relationship is necessarily forces your reader to read in-between the lines.

If you look at the list I gave above, the second bullet point relates its two clauses explicitly with the word _because_, allowing you to immediately understand that the second clause is related to the first due to providing an explanation for the first clause. In the third bullet point, the semicolon implies exactly the same relationship, but you are forced to read more carefully in order to understand that. You have to understand the two clauses separately, my implied context for writing this answer, and the parallelism in the entire list before you can be sure you correctly understand how the two halves of the sentence relate. It's not much more work, but it is more work nevertheless.

This isn't necessarily a bad thing because sometimes, that more opaque writing style is what you want. It's important to keep in mind that for writing fiction in particular, though, part of what you need to accomplish is making the task of reading your work pleasant and enjoyable for your readers. You typically want to write using a style that makes the semantic meaning of your story jump off of the page, allowing the reader to spend their mental energy on more sophisticated levels of your writing, such as the subtext in dialog or the thematic implications of characters' decisions. And, if possible, you want your writing to have a musical or poetic quality to it such that it "sounds good" in the reader's head.

Typically, a semicolon works counter to both of those goals. If you force a reader to spend some time figuring out whether your semicolon in, "I wanted to kill her; she had done so much to me," means that the speaker wants to kill her _because of_ or _in spite_ of what she had done, that's more work the reader has to do before getting back to reading in-between the lines of your story proper. And if you're trying to write with a musical quality, then forcing the reader to grind to a halt to understand a semicolon correctly can interrupt the rhythm (unless you're trying to get a slower effect).

* * *

All in all, though, these are definitely things to keep in mind at the level of being nitpicky. I would much rather read a story filled with semicolons, even awkward ones, that has compelling characters and themes than read a disjointed story with spotless prose. And every writer has their own style. Some people will never have occasion to use semicolons; others, like myself, will use them on occasion. You seem to like them, so more power to you!

When you finish your first few drafts of your story, you'll reach the point where the most important considerations aren't the structure or strength of the story proper, which have already been vetted and are largely set in stone, but rather getting the nuance and tone of each passage just so. This is the best time to consider the ideas of making your reading easy to approach and musical, and this is when you can really think carefully about each individual use of a semicolon. Until then, it's probably best to enjoy the story yourself as you discover it in the first couple drafts and not worry too much about the fine details of your prose, which you will thoroughly rework anyway.

#1: Imported from external source by user avatar System‭ · 2017-12-15T01:06:06Z (about 7 years ago)
Original score: 5