docs:

Author: meedstrom

README.org

@@ -84,7 +84,7 @@ Go to the manual and close this tab.
 - in a web browser: [[https://github.com/meedstrom/org-node/blob/main/org-node.org]]
 - or in Emacs after installation: [[info:org-node]]
 
-* Advice: Start with a paper Zettelkasten
+* Advice: Start with paper
 
 Many people on forums say that you should do *a paper slip-box first* before going digital.
 
@@ -94,11 +94,12 @@ So let me try to bootstrap you:
 
 [[file:README_5745.jpg]]
 
-If you are currently in the EU, you can order the pictured paper slips and box here:
+If you are inside the EU, you can order the pictured box and paper slips here:
 
 - https://www.123ink.se/HAN-kortlada-A6-svart-HA-976-13-i23800-t76314.html
-- https://www.123ink.se/Papper-Fotopapper/Kopieringspapper/A6/80-gram-p165367.html
+- https://www.123ink.se/123inkt-Kopieringspapper-A6-80g-vit-123ink-2-000-ark-3kg-i69137-t165367.html
+  - weirdly rare product
 
-Once these products arrive, take them and a pen with you to the local cafe, if it's a quiet noontime hour (otherwise a library, better in the afternoon).
+Once these presents have arrived, take them and a pen to the local café or library.  (If you're noise-sensitive, keep in mind that cafés are only quiet in the morning.)
 
-Then have a warm coffee, lean back, and read https://zettelkasten.de/introduction/.
+Then lean back, have a warm coffee, and read https://zettelkasten.de/introduction/.

org-node.org

@@ -6,8 +6,9 @@
 #+TEXINFO_DIR_TITLE: Org-Node: (org-node).
 #+TEXINFO_DIR_DESC: Link org-id entries into a network.
 
-This is the manual for org-node.  The [[https://github.com/meedstrom/org-node][README]] is separate, but you should not need it anymore.
+This is the instruction manual for org-node.  The [[https://github.com/meedstrom/org-node][README]] is separate, but you should not need it anymore.
 
+* Setup
 ** Installation
 
 Assuming your package manager gets recipes from [[https://melpa.org/#/getting-started][MELPA]], add the following initfile snippet.
@@ -72,13 +73,13 @@ To see a list of all commands, enter an Org buffer and type ~M-o n <f1>~.
 
 To browse config options, type ~M-x customize-group RET org-node RET~ (or ~M-o n x o~).
 
-** Backlinks
+* Backlinks
 
 Backlinks are the butter on the bread that is your notes.  If you've ever seen a "What links here" section on some webpage, that's exactly what it is.
 
 You do not have to create backlinks yourself, they are autogenerated.  The following sections outline two basic ways this can work.
 
-*** Backlink solution 1: displayed in a separate window
+** Backlink solution 1: displayed in a separate window
 - Solution 1A: Reuse the org-roam buffer ::
 
   You can use the org-roam buffer without the rest of org-roam!  Enable the following mode.
@@ -107,7 +108,7 @@ You do not have to create backlinks yourself, they are autogenerated.  The follo
   #+end_src
 
 
-*** Backlink solution 2: Print inside the file
+** Backlink solution 2: printed inside the file
 I rarely have the screen space to display a backlink buffer.  Because it needs my active involvement to keep visible, I go long periods seeing no backlinks.
 
 A complementary solution, which can also stand alone, is to have the backlinks /written into/ the file, on an Org property line or in a drawer.
@@ -179,6 +180,7 @@ A difference between org-node-context (solution 1) and org-node-backlink-mode (s
 
   Finally, lines that contain no Org link such as =[[id:1234][Title]]= are *deleted*, which would mean *destroying any other info within.*  Same if a backlink is stale and no longer valid.
 
+* Misc
 ** Org-capture
 
 You may have heard that org-roam has a set of meta-capture templates: the =org-roam-capture-templates=.
@@ -466,8 +468,8 @@ You don't need software for that basic idea, only to make it extra convenient to
 
 Thus, fundamentally, any "journal" or "dailies" software are just operating on a sorted series to navigate through.  A node sequence.  You could have sequences for, let's say, historical events, Star Trek episodes, your school curriculum...
 
-** Appendix
-*** Appendix I: Rosetta stone
+* Appendix
+** Appendix I: Rosetta stone
 
 API cheatsheet between org-roam and org-node.
 
@@ -503,7 +505,7 @@ API cheatsheet between org-roam and org-node.
 | Get =ROAM_EXCLUDE=                        |                                 | =(org-mem-entry-property "ROAM_EXCLUDE" NODE)= |
 | Ensure fresh data                       | =(org-roam-db-sync)=              | =(org-node-cache-ensure t t)=                  |
 
-*** Appendix II: How to rollback
+** Appendix II: How to rollback
 :PROPERTIES:
 :CUSTOM_ID: appendix-ii-how-to-rollback
 :END:
@@ -554,15 +556,15 @@ With [[https://github.com/radian-software/straight.el][Straight]]:
   :straight (org-node :type git :host github :repo "meedstrom/org-node"
                       :branch "v1.6"))
 #+end_src
-*** Appendix III: Random tips
-**** Fix export to HTML
+** Appendix III: Random tips
+*** Fix export to HTML
 Org-roam shipped the optional =(require 'org-roam-export)=, a patch to fix =id:= links in HTML export.
 
 Good news, upstream fixed the root of the issue in 5e9953fa0!  Update Org to 9.7+ (comes with Emacs 30), then set this.
 
 : (setq org-html-prefer-user-labels t)
 
-*** Appendix IV: What are =ROAM_REFS=?
+** Appendix IV: What are =ROAM_REFS=?
 :PROPERTIES:
 :CUSTOM_ID: appendix-iv-what-are-roam_refs
 :END:
@@ -592,10 +594,10 @@ For performance reasons, not just any string of text is accepted -- it must have
 
 Org-roam calls such backlinks /reflinks/.  In my view, adding a new word for such a similar concept just increases the air of mystery.  That's why in org-node's context buffer, they're just called "ref backlinks" -- as opposed to "ID backlinks".
 
-**** What's it actually used for?
+*** What's it actually used for?
 
 People often use it to write notes about a specific web-page or PDF file, and call it a ref-node for that resource.
 
-**** Citations
+*** Citations
 
 As a special case, citation keys such as "@ioannidis2005" also work in =ROAM_REFS=, corresponding to Org citations like =[cite:@ioannidis2005]=.

org-node.texi

@@ -21,14 +21,35 @@
 @node Top
 @top org-node
 
-This is the manual for org-node.  The @uref{https://github.com/meedstrom/org-node, README} is separate@comma{} but you should not need it anymore.
+This is the instruction manual for org-node.  The @uref{https://github.com/meedstrom/org-node, README} is separate@comma{} but you should not need it anymore.
 
 @end ifnottex
 
 @menu
+* Setup::
+* Backlinks::
+* Misc::
+* Appendix::
+
+@detailmenu
+--- The Detailed Node Listing ---
+
+Setup
+
 * Installation::
 * Quick start::
-* Backlinks::
+
+Installation
+
+* An update broke things?::
+
+Backlinks
+
+* Backlink solution 1 displayed in a separate window::
+* Backlink solution 2 printed inside the file::
+
+Misc
+
 * Org-capture::
 * Exclude uninteresting nodes::
 * Missing completions?::
@@ -42,19 +63,6 @@ This is the manual for org-node.  The @uref{https://github.com/meedstrom/org-nod
 * Limitation Org-ref::
 * Toolbox::
 * Experimental Node sequences::
-* Appendix::
-
-@detailmenu
---- The Detailed Node Listing ---
-
-Installation
-
-* An update broke things?::
-
-Backlinks
-
-* Backlink solution 1 displayed in a separate window::
-* Backlink solution 2 Print inside the file::
 
 Sort completions
 
@@ -83,8 +91,16 @@ Appendix IV: What are @samp{ROAM_REFS}?
 @end detailmenu
 @end menu
 
+@node Setup
+@chapter Setup
+
+@menu
+* Installation::
+* Quick start::
+@end menu
+
 @node Installation
-@chapter Installation
+@section Installation
 
 Assuming your package manager gets recipes from @uref{https://melpa.org/#/getting-started, MELPA}@comma{} add the following initfile snippet.
 
@@ -133,12 +149,12 @@ If you're coming here from @strong{org-roam}@comma{} try this instead:
 @end menu
 
 @node An update broke things?
-@section An update broke things?
+@subsection An update broke things?
 
 See at the end of this readme: @ref{Appendix II How to rollback, , How to rollback}
 
 @node Quick start
-@chapter Quick start
+@section Quick start
 
 If you're new to these concepts@comma{} fear not.  The main things for day-to-day operation are two commands:
 
@@ -172,7 +188,7 @@ You do not have to create backlinks yourself@comma{} they are autogenerated.  Th
 
 @menu
 * Backlink solution 1 displayed in a separate window::
-* Backlink solution 2 Print inside the file::
+* Backlink solution 2 printed inside the file::
 @end menu
 
 @node Backlink solution 1 displayed in a separate window
@@ -207,8 +223,8 @@ If you like it@comma{} consider binding it to an easily typed key@comma{} such a
 @end lisp
 @end table
 
-@node Backlink solution 2 Print inside the file
-@section Backlink solution 2: Print inside the file
+@node Backlink solution 2 printed inside the file
+@section Backlink solution 2: printed inside the file
 
 I rarely have the screen space to display a backlink buffer.  Because it needs my active involvement to keep visible@comma{} I go long periods seeing no backlinks.
 
@@ -293,8 +309,27 @@ Running aforementioned command @strong{may re-sort your backlinks and re-format
 Finally@comma{} lines that contain no Org link such as @samp{[[id:1234][Title]]} are @strong{deleted}@comma{} which would mean @strong{destroying any other info within.}  Same if a backlink is stale and no longer valid.
 @end table
 
+@node Misc
+@chapter Misc
+
+@menu
+* Org-capture::
+* Exclude uninteresting nodes::
+* Missing completions?::
+* Completion-at-point::
+* Customize appearance::
+* Sort completions::
+* Grep::
+* Let org-open-at-point detect refs::
+* Limitation TRAMP::
+* Limitation Unique titles::
+* Limitation Org-ref::
+* Toolbox::
+* Experimental Node sequences::
+@end menu
+
 @node Org-capture
-@chapter Org-capture
+@section Org-capture
 
 You may have heard that org-roam has a set of meta-capture templates: the @samp{org-roam-capture-templates}.
 
@@ -338,7 +373,7 @@ That last optional functionality may only confuse you more if I try to describe
 For deeper hacking@comma{} see @uref{https://github.com/meedstrom/org-node/wiki/Capture, wiki}.
 
 @node Exclude uninteresting nodes
-@chapter Exclude uninteresting nodes
+@section Exclude uninteresting nodes
 
 One user had over a thousand project-nodes@comma{} but only just began to do a knowledge base@comma{} and wished to avoid seeing the project nodes.
 
@@ -360,7 +395,7 @@ Or you could go with a whitelist approach@comma{} to show only nodes from a cert
 @end lisp
 
 @node Missing completions?
-@chapter Missing completions?
+@section Missing completions?
 
 Since @uref{https://github.com/meedstrom/org-mem, org-mem} only looks at saved files on disk@comma{} new notes only "appear" after save.  So it can make for a smoother experience to enable @samp{auto-save-visited-mode}.
 
@@ -374,7 +409,7 @@ That is also the usage that I test most -- I've had the following config for yea
 FWIW@comma{} org-node used to try to be smarter and also cache notes in unsaved buffers@comma{} but that quickly became difficult to reason about@comma{} especially wrt. deciding whether to update a backlink or not.
 
 @node Completion-at-point
-@chapter Completion-at-point
+@section Completion-at-point
 
 A global minor mode to complete words at point into known node titles:
 
@@ -384,7 +419,7 @@ A global minor mode to complete words at point into known node titles:
 @end lisp
 
 @node Customize appearance
-@chapter Customize appearance
+@section Customize appearance
 
 (Analogue to @samp{org-roam-node-display-template}@comma{} for those of you who know what that is)
 
@@ -401,7 +436,7 @@ A related option is @samp{org-node-alter-candidates}@comma{} which lets you matc
 @end lisp
 
 @node Sort completions
-@chapter Sort completions
+@section Sort completions
 
 A useful way to sort completions is to base it on a @samp{:TIME_MODIFIED:} property under each of your ID-nodes.
 
@@ -425,7 +460,7 @@ Then to start actually sorting nodes by their @samp{:TIME_MODIFIED:} values:
 @end menu
 
 @node Bonus Lining up properties
-@section Bonus: Lining up properties
+@subsection Bonus: Lining up properties
 
 I want to see @samp{:TIME_CREATED:} right above @samp{:TIME_MODIFIED:}.
 
@@ -448,7 +483,7 @@ So I re-sort the entire properties drawer on save:
 @end lisp
 
 @node Grep
-@chapter Grep
+@section Grep
 
 If you have Ripgrep installed on the computer@comma{} and @uref{https://github.com/minad/consult, Consult} installed on Emacs@comma{} you can use this command to grep across all your Org files at any time.
 
@@ -473,7 +508,7 @@ Type @code{C-c C-c} to apply the changes
 @end enumerate
 
 @node Let org-open-at-point detect refs
-@chapter Let org-open-at-point detect refs
+@section Let org-open-at-point detect refs
 
 (For background@comma{} see @ref{Appendix IV What are @samp{ROAM_REFS}?, , What are ROAM@math{_REFS}?} at the end of this README@.)
 
@@ -487,14 +522,14 @@ Wouldn't it be nice if@comma{} clicking on that link@comma{} you automatically v
 @end lisp
 
 @node Limitation TRAMP
-@chapter Limitation: TRAMP
+@section Limitation: TRAMP
 
 Working with files over TRAMP is unsupported@comma{} because org-mem works in parallel subprocesses which do not inherit your TRAMP setup.
 
 The best way to change this is to @uref{https://github.com/meedstrom/org-mem/issues, file an issue} to show you care :-)
 
 @node Limitation Unique titles
-@chapter Limitation: Unique titles
+@section Limitation: Unique titles
 
 If two ID-nodes exist with the same title@comma{} one of them disappears from minibuffer completions.
 
@@ -511,7 +546,7 @@ This lets you match against the node outline path and not only the title@comma{}
 NB: for users of @samp{org-node-complete-at-point-mode}@comma{} this workaround won't help those completions.  With some luck you'll link to the wrong one of two homonymous nodes@comma{} but it's worth being aware. (@uref{https://github.com/meedstrom/org-node/issues/62, #62})
 
 @node Limitation Org-ref
-@chapter Limitation: Org-ref
+@section Limitation: Org-ref
 
 Org-node supports the Org 9.5 @@citations@comma{} but not fully the aftermarket @uref{https://github.com/jkitchin/org-ref, org-ref} &citations that emulate @LaTeX{} look-and-feel.
 
@@ -530,7 +565,7 @@ Contribute to @uref{https://github.com/meedstrom/org-mem, org-mem}@comma{} see f
 @end itemize
 
 @node Toolbox
-@chapter Toolbox
+@section Toolbox
 
 (Note that you can view this same list of commands in Emacs.  Assuming that @samp{M-o n} was where you bound @samp{org-node-org-prefix-map}@comma{} type @samp{M-o n <f1>}.)
 
@@ -676,7 +711,7 @@ Rarer commands for org-node-backlink-mode:
 @end itemize
 
 @node Experimental Node sequences
-@chapter Experimental: Node sequences
+@section Experimental: Node sequences
 
 Do you already know about "daily-notes"?  Then get started as follows:
 
@@ -698,7 +733,7 @@ Tip: Consider binding a shorter key @code{M-o s}
 @end menu
 
 @node What are node seqs?
-@section What are node seqs?
+@subsection What are node seqs?
 
 It's easiest to explain node sequences if we use "daily-notes" (aka "dailies") as an example.