写作方法2017matt.might.net
用 Shell 脚本改善你的文笔
Shell scripts to improve your writing
导读
这篇介绍一组用 shell 脚本自动标出被动语态、模糊限定语和重复词的写作检查方法，并延伸到 GNU diction/style 与 Emacs writegood 等工具。它适合写作者了解如何把机械校对交给工具、把判断留给人：这类检查能加快润色，但不能代替结构和语境判断。
可以直接用的写作要点
- 01
把被动语态、模糊限定语和重复词做成脚本或编辑器提示，初稿后先跑一遍再人工删改。
- 02
工具只负责“标出来”，不要机械删除；被动语态、副词和必要限定语在合适语境中有效。
- 03
用 GNU diction/style 等工具检查冗词、误用短语和句长等可读性指标，但别指望它帮你搭结构。
- 04
将检查集成到 Emacs writegood 或邮件/文档编辑器，缩短校对时间；对误报和歧义指代仍需人工判断。
HN 评论精选
推荐用 GNU diction/style 补充检查冗词、误用短语和可读性，但别指望它处理结构。
还有 GNU style 和 GNU diction（https://www.gnu.org/software/diction/）。Diction 和 Style 是两个老牌 Unix 命令：Diction 找出冗长和常见误用短语，Style 分析句子长度等表层可读性指标。它们不能帮你把文档结构写好，但能帮你避免糟糕措辞，并比较文档的可读性（不是可理解性）；两者都支持英文和德文。示例中 diction 对一段文字标出了 “they/can/compare” 等可疑用法，并报告 5 句中发现 3 个短语。
erlehmann_查看英文原文
There is also GNU style and GNU diction: https://www.gnu.org/software/diction/ ; cat <<EOF >/tmp/testfile Diction and style are two old standard Unix commands. Diction identifies wordy and commonly misused phrases. Style analyses surface characteristics of a document, including sentence length and other readability measures. These programs cannot help you structure a document well, but they can help to avoid poor wording and compare the readability (not the understandability!) of your documents with others. Both commands support English and German documents. EOF ; LANG=C diction --lang en --suggest /tmp/testfile /tmp/testfile:2: These programs cannot help you structure a document well, but [they -> (do not use as substitute for "each, each one, everybody, every one, anybody, any one, somebody, some one")] [can -> (do not confuse with "may")] help to avoid poor wording and [compare -> "Compare" to points out resemblances, "compare with" points out differences.] the readability (not the understandability!) of your documents with others. 3 phrases in 5 sentences found.
反对把 Strunk & White 和“禁用被动/副词”等规则绝对化，工具标记要结合语境。
小学以后就不该再把 Strunk and White 当风格指南；被动语态、副词以及他提到的其他东西本身都没什么错。他连 weasel words 是什么都没说对（如“some people say”“it is believed”）；我也不觉得“very close match”就比“close match”更带主观判断——后者也并非精确定义。
empath75查看英文原文
Nobody should be using Strunk and White as a style guide after primary school. There's nothing fundamentally wrong with passive voice, or adverbs, or any of the other things that he mentions here. http://www.chronicle.com/article/50-Years-of-Stupid-Grammar/25497 He doesn't even correctly identify what weasel words are. ("Some people say", "It is believed", etc). I'm not sure why 'very close match' is any more opinionated than 'close match' is. It's not as if the latter is precisely defined.
把这类检查集成进编辑器，形成即时反馈的写作工作流。
我读全文时一直想“这应该做成一个 Emacs 模式！”结果文末正好提到：Benjamin Beckwith 受这些脚本启发写了 Emacs 的“writegood”模式。我现在就把它加进 .emacs。
randomstring查看英文原文
I read the whole article thinking "this needs to be an emacs mode!" only to get to the punchline at the bottom. >> Benjamin Beckwith has contributed a "writegood" mode for emacs inspired by these scripts. This is going into my .emacs right now.
期待自动校对覆盖长句、重复词和歧义指代，但误报是普及障碍。
Google Docs、Gmail 或 Atom 有没有类似工具？拼写检查已经普及几十年，但自动语法和校对检查还不常见，我觉得很奇怪。比如让邮件客户端高亮过长的句子、重复词、歧义指代（如“it”指哪个名词）等，肯定能省校对时间，实现起来似乎也不难；我隔几天就能看到有人把 loose/lose 用错。不过很多语法检查器误报不少，这项技术还没进步吗？
seanwilson查看英文原文
Is there anything like this for Google Docs, Gmail or Atom? We've had spellcheckers for decades but I find it really surprising that automated grammar and proofreading checkers aren't in common use yet. For example, having my email client highlight overly long sentences, duplicate words, ambiguous references (e.g. what noun does "it" refer to) and more would undoubtable save proofreading time and doesn't sounds that difficult to implement. I see online comments every few days of someone pointing out the word loose/lose is used incorrectly for instance. I recall that many grammar checkers suffer from false positives though but has the technology not advanced?
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。
写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选书面沟通是远程工作的超级能力
Written communication is remote work super power
这篇文章讨论远程工作中书面沟通的价值，评论区则补充了异步与同步沟通的适用场景，并提醒读者：备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。
写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选如何写出有用的文字
How to Write Usefully
保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式：有用≈重要×新颖×正确×清楚，任一项为零，整篇文章就等于零；他还主张敢下确定判断、删掉让自己心虚的句子。
写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选如何写得更清楚、想得更清楚，并学会复杂材料（PDF）
How to write more clearly, think more clearly, and learn complex material [pdf]
这份 PDF 讨论如何把文章写清楚、把思路理清楚，并用写作来学习复杂材料。
写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选