工具与资源doc.norang.ca
用纯文本的 Org Mode 组织你的人生
Org Mode – Organize Your Life in Plain Text
2009 — 2020，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这是 Bernt Hansen 维护的一份 Org Mode 使用手册，详细记录他如何用 Emacs 的 Org Mode 安排任务、日程、笔记与项目，内容包括大量配置代码、快捷键和自定义 agenda 视图。它更像一份完整工作流的实录，并非入门教程：照着抄就能搭起一套纯文本的个人管理系统。
为什么经久不衰：它展示了纯文本系统能被定制和长期维护到什么程度，十多年后仍是 Org Mode 工作流最完整的参考范本之一。
HN 评论精选
易上手的工具会在长期使用后变成天花板，org-mode 消除了这种沉没成本风险。
很多人说花几十小时学 org-mode“不值得”，因为有 Evernote、Trello、Todoist 这类直觉好用的工具。但他们忽略了一点：低门槛有时会在后期变成增长的天花板，而那时你已经投入了几千小时。我曾在 Evernote 里存学术笔记，大约两千条、几年之后就成了地狱：需要时找不到，也不支持非线性工作方式，它成了只吞信息不吐信息的黑洞。用 org-mode 我搭了自己的归档与研究系统，几千篇文章之后仍然能快速找到东西；现在配合 org-roam，我可以建立知识枢纽，不必担心线性或时间顺序。不喜欢某个流程，我可以随时改造它。
madballster查看英文原文
I see a lot of comments arguing that it's not "worth it" to spend dozens of hours to "get into org-mode" when there are "intuitive tools" such as Evernote or Trello or Todoist etc. What some are missing is the fact that low barriers to entry sometimes turn into barriers to growth at a later stage. After (!) one has sunk thousands of hours into them. I used to keep my academic notes in Evernote and it turned into hell after about 2,000 notes and a few years of work. I couldn't find things when I needed them, it didn't support a non-linear mode of work. It became my personal black hole that swallowed up information but never gave it back. With org-mode I have created my very own filing and research system. After years of using it and thousands of articles I find things. Quickly. Now, with org-roam, I create hubs of knowledge and ideas that I can come back to at a later point without worrying about linearity or chronology. No longer do I need to know where things are. I know what ideas are in there. If I don't like a certain workflow, I can grow, develop or change my filing and note-taking system as I see fit. In my opinion, org-mode eliminates the risk of hitting any sort of barrier after years of sunk costs.
标题里的“纯文本”言过其实，这份文档本身就是大量 Emacs 配置的堆砌。
Org Mode 一再被推荐，但这个标题实在是我见过最大胆的说法之一。看看这份文档：400 多 KB 的 HTML 页面，全是 Emacs 配置、快捷键之类，除非你多年是 Emacs 重度用户，否则完全看不懂。所谓“纯文本”在哪里？输出也许像纯文本，但它显然不是。我不反对它和它的用户，只是请现实一点。
birracerveza查看英文原文
Org Mode keeps being pushed again and again, but honestly this title is one of the boldest claims I've seen about it. Just look at the document. It's a 400+kb HTML page of Emacs configurations, keybindings and other stuff that makes absolutely no sense unless you've been an avid Emacs user for years. Where is the Plain Text here? I see nothing of the sort. Sure, the output might resemble Plain Text, but it's clearly not. I have nothing against it or those who use it, more power to you, but please be realistic. Sorry about the rant.
用“纯文本”来推销 org-mode 是错的，它的价值在于整个 Emacs 系统的整合能力。
我用 Emacs 和 org-mode 大约四年了，一直觉得它的宣传方式有问题：总强调“纯文本”，于是非 Emacs 用户会问“那我为什么不继续用自己的文本编辑器”。Emacs 的价值不能按单个功能来衡量，哪怕 org-mode 本身很强大，你得把整个系统及其可能性一起看。org-mode 特别之处在于它整合了 Emacs 的众多能力：文学编程、Wiki、日程、日记、文件浏览、记账、邮件等等。单看 org-mode 一个包，就像用座椅质量来评判一辆车。我唯一能比的体验反而是 Office 365：价值不在某个应用，而在整合。
nanna查看英文原文
Having been using Emacs and org-mode for about 4 years now, I've been thinking a big mistake has been made in how the system is pitched. It's always something about it being 'plain text', which makes non-Emacs users say 'Why would I switch from my plain text editor? Or 'Why would I switch from a flashy GUI webapp version of this particular feature?' Emacs can't be appreciated for any one feature, even org mode, powerful as that is. You have to take the entire system and all it's possibilities into account. Org mode is particularly special because it integrates so many of Emacs' features, from literate programming to keeping a Wiki, to scheduling, to keeping a diary, to file browsing, to accounting, to emailing, to so much more. But to try to judge one package like org mode is a bit like judging a car by the quality of its seats. The only thing I've experienced which compares to this is, perversely, the Office 365 suite. Yes, of course, all the functions are completely different and I'm not making a like-for-like functionality comparison. But in Office365 an email client (Outlook) is integrated with a team's documents (via Sharepoint), chats (via Teams), calendar, etc, etc. The value of Office365 isn't in any one app, it's their integration. It's the entire system. Obviously the Emacs system has a completely different and opposing design philosophy to Office365's. It's ground-up, fully-extendable, initially demanding, text based, exportable, self-hosted, free, and so on. All of which increasingly goes against the grain of the trajectory of software today. However for those who give it the time and effort, it really does offer to organise your life, and yes, in plain text.
他主张仅按日期组织日志、靠关键词搜索，认为 Org Mode 在录入阶段的结构化成本过高。
从 2005 年起我就把带日期的文本文件放在 Log 文件夹里，按年月组织。需要数字草稿纸时就留着它；要保存文件时，我就打开一个带日期的日志文件夹。这里有个年轻人常搞错的优化问题：要像哈夫曼编码那样，权衡录入时花在组织上的工夫和日后检索的工夫。比如我把纸质收据按季度丢进四个轮换的箱子，旧的抽真空存到车库——偶尔能靠它证明发货省下几百美元，但录入时再多花工夫就是错误。我的日志之所以好用，恰恰因为除了日期没有任何组织结构；我改为练好在内容里写关键词，总是问“以后我会怎么找它”，从不用纠结归到“花园”还是“番茄”，直接全系统搜索。而且这套系统熬过了多次编辑器迁移。我同意别用商业系统，那就像在茶几上摆一本理想菜谱；而 Org Mode 对录入来说又太结构化了，对我不够最优。
Syzygies查看英文原文
Starting in 2005, I've been keeping dated text files in a Log folder, organized by year and month. Anytime I need digital "scrap paper" I make sure I keep it. If I need to save files, I open instead a dated log folder. There's a critical optimization problem here the young often get wrong. One needs to "Huffman code" the work put into organizing on entry, versus the work later in retrieving. For example, I save physical receipts into four rotating bins by quarter, then I vacuum pack the old receipts and stash them in the garage. Occasionally I save hundreds of dollars by proving I shipped something (and that would be a receipt I probably scanned) but any more work than this on entry would be a mistake. It's the complete lack of organizational structure, other than date, that make my log files so useful. I instead get good at including keywords, always asking how I would find this later. I never have to wonder whether I filed this under "garden" or "tomatoes", resorting to a system-wide search. And this system has survived many editor migrations. I agree with the arguments not to use a commercial system. That's like putting an aspirational cookbook on your coffee table. Org Mode is also too structured on entry to be optimal for me.
历次讨论
同类还值得读
直接在浏览器中启动 Linux 内核
Boot a linux kernel right inside your browser.
Fabrice Bellard 的 JSLinux 页面，用 JavaScript 在浏览器里启动一个 Linux 内核，并提供一个可交互的终端环境。
工具与资源上首页 5 次 · 2011–2025bellard.orgHacker News 未公开功能与行为清单（2018）
A List of Hacker News's Undocumented Features and Behaviors (2018)
数据科学家 Max Woolf 整理的 Hacker News 未公开功能与行为清单，涵盖投票机制、排名算法、账号惩罚等社区运作细节。
工具与资源上首页 5 次 · 2019–2025github.comMapSCII：在终端中用盲文和 ASCII 渲染地图
MapSCII – Braille and ASCII map renderer for the console
MapSCII 是一个在命令行终端里渲染地图的开源工具，用盲文字符和 ASCII 字符把地理数据画成可交互浏览的字符地图。
工具与资源上首页 5 次 · 2017–2025github.com顶尖大学的免费在线课程
Free Online Courses from Top Universities
Open Culture 整理的一份免费在线课程合集，汇集了全球顶尖大学（如 MIT、斯坦福、耶鲁等）向公众开放的网络课程资源，涵盖音频、视频等多种形式。
工具与资源上首页 5 次 · 2010–2022openculture.com淘气字符串：容易引发用户输入问题的字符串清单
Naughty Strings: A list of strings likely to cause issues as user-input data
一个 GitHub 仓库，收录了大量容易让程序出问题的用户输入字符串，如特殊字符、emoji、SQL 注入片段、系统命令等，供开发者用于测试输入处理逻辑。
工具与资源上首页 4 次 · 2015–2020github.com