apex-ruby 1.0.6 → 1.0.7

data/ext/apex_ext/apex_src/man/apex-config.5

@@ -1,374 +1,449 @@
-.\" Automatically generated by Pandoc 3.8.3
-.\"
-.TH "APEX\-CONFIG" "5" "December 2025" ""
+.TH "NAME" "1" "1 January 1970" ""
+
 .SH NAME
+
+.PP
 apex\-config \- Apex configuration file format
+
 .SH DESCRIPTION
-Apex supports flexible configuration through metadata files that allow
-you to define defaults once and reuse them across many documents, while
-still allowing per\-document and per\-invocation overrides.
+
+.PP
+Apex supports flexible configuration through metadata files that allow you to define defaults once and reuse them across many documents, while still allowing per\-document and per\-invocation overrides.
+
 .PP
 Configuration can come from three main sources:
-.IP "1." 3
-\f[B]Global configuration file\f[R] \-
-\f[CR]$XDG_CONFIG_HOME/apex/config.yml\f[R] or
-\f[CR]\(ti/.config/apex/config.yml\f[R]
-.IP "2." 3
-\f[B]External metadata files\f[R] \- Any file passed via
-\f[CR]\-\-meta\-file\f[R]
-.IP "3." 3
-\f[B]Per\-document metadata\f[R] \- YAML, MultiMarkdown, or
-Pandoc\-style metadata in the document
+
+.IP "1." 4
+\f[B]Global configuration file\f[] \- \fR$XDG_CONFIG_HOME/apex/config.yml\f[] or \fR~/.config/apex/config.yml\f[]
+
+.IP "2." 4
+\f[B]External metadata files\f[] \- Any file passed via \fR\-\-meta\-file\f[]
+
+.IP "3." 4
+\f[B]Per\-document metadata\f[] \- YAML, MultiMarkdown, or Pandoc\-style metadata in the document
+
 .PP
 Command\-line flags always override configuration file settings.
+
 .SH GLOBAL CONFIG FILE
-When you run \f[B]apex\f[R](1) without an explicit
-\f[CR]\-\-meta\-file\f[R], Apex automatically checks for a global
-configuration file:
+
+.PP
+When you run \f[B]apex\f[](1) without an explicit \fR\-\-meta\-file\f[], Apex automatically checks for a global configuration file:
+
 .IP \(bu 2
-If \f[CR]$XDG_CONFIG_HOME\f[R] is set:
-\f[CR]$XDG_CONFIG_HOME/apex/config.yml\f[R]
+If \fR$XDG_CONFIG_HOME\f[] is set: \fR$XDG_CONFIG_HOME/apex/config.yml\f[]
+
 .IP \(bu 2
-Otherwise: \f[CR]\(ti/.config/apex/config.yml\f[R]
+Otherwise: \fR~/.config/apex/config.yml\f[]
+
 .PP
-If the file exists, Apex loads it as if you had passed it via
-\f[CR]\-\-meta\-file\f[R], and merges its metadata with the document and
-any \f[CR]\-\-meta\f[R] command\-line metadata.
+If the file exists, Apex loads it as if you had passed it via \fR\-\-meta\-file\f[], and merges its metadata with the document and any \fR\-\-meta\f[] command\-line metadata.
+
 .PP
-This makes \f[CR]config.yml\f[R] ideal for defining project\-agnostic
-defaults such as:
+This makes \fRconfig.yml\f[] ideal for defining project\-agnostic defaults such as:
+
 .IP \(bu 2
-Default \f[CR]mode\f[R] (e.g.\ \f[CR]unified\f[R], \f[CR]gfm\f[R],
-\f[CR]mmd\f[R])
+Default \fRmode\f[] (e.g. \fRunified\f[], \fRgfm\f[], \fRmmd\f[])
+
 .IP \(bu 2
-Default \f[CR]language\f[R] and \f[CR]quoteslanguage\f[R]
+Default \fRlanguage\f[] and \fRquoteslanguage\f[]
+
 .IP \(bu 2
-Common feature flags (\f[CR]pretty\f[R], \f[CR]standalone\f[R],
-\f[CR]indices\f[R], \f[CR]wikilinks\f[R], etc.)
+Common feature flags (\fRpretty\f[], \fRstandalone\f[], \fRindices\f[], \fRwikilinks\f[], etc.)
+
 .IP \(bu 2
 Default bibliography style
-.SS Example \f[CR]config.yml\f[R]
-.IP
-.EX
+
+.SS Example \fRconfig.yml\f[]
+
+.PP
+.nf
+\fR
 \-\-\-
-\f[I]# Default processor mode and output style\f[R]
-mode\f[B]:\f[R] unified
-standalone\f[B]:\f[R] true
-pretty\f[B]:\f[R] true
-
-\f[I]# Locale and quotation style\f[R]
-language\f[B]:\f[R] en
-quoteslanguage\f[B]:\f[R] english
-
-\f[I]# Common feature flags\f[R]
-autolink\f[B]:\f[R] true
-includes\f[B]:\f[R] true
-relaxed\-tables\f[B]:\f[R] true
-sup\-sub\f[B]:\f[R] true
-
-\f[I]# Index and bibliography defaults\f[R]
-indices\f[B]:\f[R] true
-group\-index\-by\-letter\f[B]:\f[R] true
-bibliography\f[B]:\f[R] references.bib
-csl\f[B]:\f[R] apa.csl
+# Default processor mode and output style
+mode: unified
+standalone: true
+pretty: true
+# Locale and quotation style
+language: en
+quoteslanguage: english
+# Common feature flags
+autolink: true
+includes: true
+relaxed\-tables: true
+sup\-sub: true
+# Index and bibliography defaults
+indices: true
+group\-index\-by\-letter: true
+bibliography: references.bib
+csl: apa.csl
+# Syntax highlighting (optional)
+code\-highlight: pygments
+code\-line\-numbers: true
+highlight\-language\-only: true
 \-\-\-
-.EE
+
+\f[]
+.fi
+
 .SH EXTERNAL METADATA FILES
-For project\-specific or task\-specific configurations, use
-\f[CR]\-\-meta\-file\f[R] to point to a reusable metadata file:
-.IP
-.EX
+
+.PP
+For project\-specific or task\-specific configurations, use \fR\-\-meta\-file\f[] to point to a reusable metadata file:
+
+.PP
+.nf
+\fR
 apex document.md \-\-meta\-file project\-defaults.yml
-.EE
+
+\f[]
+.fi
+
 .PP
-These files use the same metadata keys as \f[CR]config.yml\f[R] and
-document front matter.
+These files use the same metadata keys as \fRconfig.yml\f[] and document front matter.
+
 .SS Example project config
-.IP
-.EX
+
+.PP
+.nf
+\fR
+\-\-\-
+mode: unified
+standalone: true
+pretty: true
+# Project\-specific bibliography
+bibliography: project\-refs.bib
+csl: chicago\-note\-bibliography.csl
+# Enable wiki links and relaxed tables for this project
+wikilinks: true
+relaxed\-tables: true
 \-\-\-
-mode\f[B]:\f[R] unified
-standalone\f[B]:\f[R] true
-pretty\f[B]:\f[R] true
 
-\f[I]# Project\-specific bibliography\f[R]
-bibliography\f[B]:\f[R] project\-refs.bib
-csl\f[B]:\f[R] chicago\-note\-bibliography.csl
+\f[]
+.fi
 
-\f[I]# Enable wiki links and relaxed tables for this project\f[R]
-wikilinks\f[B]:\f[R] true
-relaxed\-tables\f[B]:\f[R] true
-\-\-\-
-.EE
 .SH PER\-DOCUMENT METADATA
-Each document can define its own metadata in YAML, MultiMarkdown, or
-Pandoc formats.
-Apex extracts this metadata before processing, merges it with any
-file/config metadata, and then applies it to options.
+
+.PP
+Each document can define its own metadata in YAML, MultiMarkdown, or Pandoc formats. Apex extracts this metadata before processing, merges it with any file/config metadata, and then applies it to options.
+
 .SS YAML front matter example
-.IP
-.EX
-\f[I]\-\-\-\f[R]
-\f[BI]title:\f[R]\f[I] My Research Paper\f[R]
-\f[BI]author:\f[R]\f[I] Jane Doe\f[R]
-\f[BI]mode:\f[R]\f[I] unified\f[R]
-\f[BI]standalone:\f[R]\f[I] true\f[R]
-\f[BI]pretty:\f[R]\f[I] true\f[R]
-\f[BI]indices:\f[R]\f[I] false\f[R]
-\f[BI]wikilinks:\f[R]\f[I] true\f[R]
-\f[BI]bibliography:\f[R]\f[I] references.bib\f[R]
-\f[BI]language:\f[R]\f[I] en\f[R]
-\f[BI]quoteslanguage:\f[R]\f[I] english\f[R]
-\f[I]\-\-\-\f[R]
 
+.PP
+.nf
+\fR
+\-\-\-
+title: My Research Paper
+author: Jane Doe
+mode: unified
+standalone: true
+pretty: true
+indices: false
+wikilinks: true
+bibliography: references.bib
+language: en
+quoteslanguage: english
+\-\-\-
 # Introduction
 \&...
-.EE
+
+\f[]
+.fi
+
 .SS MultiMarkdown metadata example
-.IP
-.EX
-\f[BI]Title:\f[R]\f[I] My Research Paper\f[R]
-\f[BI]Author:\f[R]\f[I] Jane Doe\f[R]
-\f[BI]Mode:\f[R]\f[I] unified\f[R]
-\f[BI]Standalone:\f[R]\f[I] true\f[R]
-\f[BI]Pretty:\f[R]\f[I] true\f[R]
-\f[BI]Indices:\f[R]\f[I] false\f[R]
-\f[BI]WikiLinks:\f[R]\f[I] true\f[R]
-\f[BI]Bibliography:\f[R]\f[I] references.bib\f[R]
-\f[BI]Language:\f[R]\f[I] en\f[R]
-\f[BI]Quotes Language:\f[R]\f[I] english\f[R]
 
+.PP
+.nf
+\fR
+Title: My Research Paper
+Author: Jane Doe
+Mode: unified
+Standalone: true
+Pretty: true
+Indices: false
+WikiLinks: true
+Bibliography: references.bib
+Language: en
+Quotes Language: english
 # Introduction
 \&...
-.EE
+
+\f[]
+.fi
+
 .PP
-Apex normalizes keys (case\-insensitive, ignores spaces and dashes), so
-\f[CR]Quotes Language\f[R], \f[CR]quoteslanguage\f[R], and
-\f[CR]quotes\-language\f[R] are treated equivalently.
+Apex normalizes keys (case\-insensitive, ignores spaces and dashes), so \fRQuotes Language\f[], \fRquoteslanguage\f[], and \fRquotes\-language\f[] are treated equivalently.
+
 .SH PRECEDENCE AND MERGING
-When Apex builds the final configuration for a run, it merges all
-sources in this order:
-.IP "1." 3
-\f[B]File metadata\f[R] (lowest precedence)
-.RS 4
+
+.PP
+When Apex builds the final configuration for a run, it merges all sources in this order:
+
+.IP "1." 4
+\f[B]File metadata\f[] (lowest precedence)
+
 .IP \(bu 2
-Global \f[CR]config.yml\f[R] if present and no explicit
-\f[CR]\-\-meta\-file\f[R] was given
+Global \fRconfig.yml\f[] if present and no explicit \fR\-\-meta\-file\f[] was given
+
 .IP \(bu 2
-Any metadata file provided via \f[CR]\-\-meta\-file\f[R]
-.RE
-.IP "2." 3
-\f[B]Document metadata\f[R]
-.RS 4
+Any metadata file provided via \fR\-\-meta\-file\f[]
+
+.IP "2." 4
+\f[B]Document metadata\f[]
+
 .IP \(bu 2
 YAML/MultiMarkdown/Pandoc metadata inside the document
-.RE
-.IP "3." 3
-\f[B]Command\-line metadata\f[R]
-.RS 4
-.IP \(bu 2
-Values passed via \f[CR]\-\-meta KEY=VALUE\f[R]
-.RE
-.IP "4." 3
-\f[B]Command\-line flags\f[R]
-.RS 4
-.IP \(bu 2
-Flags like \f[CR]\-\-mode\f[R], \f[CR]\-\-pretty\f[R],
-\f[CR]\-\-no\-tables\f[R], etc.
-.RE
+
+.IP "3." 4
+\f[B]Command\-line metadata\f[]
+
+.IP \(bu 2
+Values passed via \fR\-\-meta KEY=VALUE\f[]
+
+.IP "4." 4
+\f[B]Command\-line flags\f[]
+
+.IP \(bu 2
+Flags like \fR\-\-mode\f[], \fR\-\-pretty\f[], \fR\-\-no\-tables\f[], etc.
+
 .PP
-Later sources override earlier ones.
-In practice:
+Later sources override earlier ones. In practice:
+
 .IP \(bu 2
-A document can override defaults from \f[CR]config.yml\f[R] or
-\f[CR]\-\-meta\-file\f[R]
+A document can override defaults from \fRconfig.yml\f[] or \fR\-\-meta\-file\f[]
+
 .IP \(bu 2
-\f[CR]\-\-meta\f[R] values can override both document and file metadata
+\fR\-\-meta\f[] values can override both document and file metadata
+
 .IP \(bu 2
 Explicit CLI flags still behave as final overrides where applicable
+
 .PP
-\f[B]Note:\f[R] If \f[CR]mode\f[R] is specified in metadata (file or
-document), Apex resets options to that mode\(cqs defaults before
-applying other metadata keys, so the mode behaves as if you had passed
-it on the command line first.
+\f[B]Note:\f[] If \fRmode\f[] is specified in metadata (file or document), Apex resets options to that mode’s defaults before applying other metadata keys, so the mode behaves as if you had passed it on the command line first.
+
 .SH CONFIGURATION KEYS
-Configuration keys correspond closely to Apex command\-line options.
-Most options can be controlled via metadata in \f[CR]config.yml\f[R],
-\f[CR]\-\-meta\-file\f[R] files, or per\-document metadata.
+
+.PP
+Configuration keys correspond closely to Apex command\-line options. Most options can be controlled via metadata in \fRconfig.yml\f[], \fR\-\-meta\-file\f[] files, or per\-document metadata.
+
 .SS Boolean options
+
+.PP
 Boolean keys accept any of the following values (case\-insensitive):
+
 .IP \(bu 2
-\f[CR]true\f[R] / \f[CR]false\f[R]
+\fRtrue\f[] / \fRfalse\f[]
+
 .IP \(bu 2
-\f[CR]yes\f[R] / \f[CR]no\f[R]
+\fRyes\f[] / \fRno\f[]
+
 .IP \(bu 2
-\f[CR]1\f[R] / \f[CR]0\f[R]
+\fR1\f[] / \fR0\f[]
+
 .PP
-\f[B]Supported boolean keys include:\f[R]
+\f[B]Supported boolean keys include:\f[]
+
 .IP \(bu 2
-\f[CR]indices\f[R] \- Enable index processing
+\fRindices\f[] \- Enable index processing
+
+.IP \(bu 2
+\fRwikilinks\f[] \- Enable wiki link syntax (\fR[[Page]]\f[])
+
+.IP \(bu 2
+\fRwikilink\-sanitize\f[] \- Sanitize wiki link URLs (lowercase, remove apostrophes, clean non\-alphanumeric)
+
 .IP \(bu 2
-\f[CR]wikilinks\f[R] \- Enable wiki link syntax (\f[CR][[Page]]\f[R])
+\fRincludes\f[] \- Enable file inclusion
+
 .IP \(bu 2
-\f[CR]includes\f[R] \- Enable file inclusion
+\fRrelaxed\-tables\f[] \- Enable relaxed table parsing
+
 .IP \(bu 2
-\f[CR]relaxed\-tables\f[R] \- Enable relaxed table parsing
+\fRalpha\-lists\f[] \- Enable alphabetic list markers
+
+.IP \(bu 2
+\fRmixed\-lists\f[] \- Allow mixing list marker types at the same level
+
 .IP \(bu 2
-\f[CR]alpha\-lists\f[R] \- Enable alphabetic list markers
+\fRsup\-sub\f[] \- Enable MultiMarkdown\-style superscript/subscript
+
 .IP \(bu 2
-\f[CR]mixed\-lists\f[R] \- Allow mixing list marker types at the same
-level
+\fRautolink\f[] \- Enable automatic URL/email linking
+
 .IP \(bu 2
-\f[CR]sup\-sub\f[R] \- Enable MultiMarkdown\-style superscript/subscript
+\fRtransforms\f[] \- Enable metadata transforms (\fR[%key:transform]\f[])
+
 .IP \(bu 2
-\f[CR]autolink\f[R] \- Enable automatic URL/email linking
+\fRunsafe\f[] \- Allow raw HTML in output
+
 .IP \(bu 2
-\f[CR]transforms\f[R] \- Enable metadata transforms
-(\f[CR][%key:transform]\f[R])
+\fRtables\f[] \- Enable/disable table support
+
 .IP \(bu 2
-\f[CR]unsafe\f[R] \- Allow raw HTML in output
+\fRfootnotes\f[] \- Enable/disable footnote support
+
 .IP \(bu 2
-\f[CR]tables\f[R] \- Enable/disable table support
+\fRsmart\f[] \- Enable/disable smart typography
+
 .IP \(bu 2
-\f[CR]footnotes\f[R] \- Enable/disable footnote support
+\fRmath\f[] \- Enable/disable math support
+
 .IP \(bu 2
-\f[CR]smart\f[R] \- Enable/disable smart typography
+\fRids\f[] \- Enable/disable automatic header IDs
+
 .IP \(bu 2
-\f[CR]math\f[R] \- Enable/disable math support
+\fRheader\-anchors\f[] \- Use \fR<a>\f[] anchors instead of plain \fRid\f[] attributes
+
 .IP \(bu 2
-\f[CR]ids\f[R] \- Enable/disable automatic header IDs
+\fRembed\-images\f[] \- Enable base64 image embedding
+
 .IP \(bu 2
-\f[CR]header\-anchors\f[R] \- Use \f[CR]<a>\f[R] anchors instead of
-plain \f[CR]id\f[R] attributes
+\fRlink\-citations\f[] \- Link citations to bibliography entries
+
 .IP \(bu 2
-\f[CR]embed\-images\f[R] \- Enable base64 image embedding
+\fRshow\-tooltips\f[] \- Add tooltips to citations
+
 .IP \(bu 2
-\f[CR]link\-citations\f[R] \- Link citations to bibliography entries
+\fRsuppress\-bibliography\f[] \- Suppress bibliography output
+
 .IP \(bu 2
-\f[CR]show\-tooltips\f[R] \- Add tooltips to citations
+\fRsuppress\-index\f[] \- Suppress index output while still creating markers
+
 .IP \(bu 2
-\f[CR]suppress\-bibliography\f[R] \- Suppress bibliography output
+\fRgroup\-index\-by\-letter\f[] \- Group index entries alphabetically
+
 .IP \(bu 2
-\f[CR]suppress\-index\f[R] \- Suppress index output while still creating
-markers
+\fRobfuscate\-emails\f[] \- Hex\-encode \fRmailto:\f[] links and visible email addresses
+
 .IP \(bu 2
-\f[CR]group\-index\-by\-letter\f[R] \- Group index entries
-alphabetically
+\fRpretty\f[] \- Pretty\-print HTML
+
 .IP \(bu 2
-\f[CR]obfuscate\-emails\f[R] \- Hex\-encode \f[CR]mailto:\f[R] links and
-visible email addresses
+\fRstandalone\f[] \- Generate a full HTML document (\fR<html>\f[], \fR<head>\f[], \fR<body>\f[])
+
 .IP \(bu 2
-\f[CR]pretty\f[R] \- Pretty\-print HTML
+\fRhardbreaks\f[] \- Treat newlines as \fR<br>\f[]
+
 .IP \(bu 2
-\f[CR]standalone\f[R] \- Generate a full HTML document
-(\f[CR]<html>\f[R], \f[CR]<head>\f[R], \f[CR]<body>\f[R])
+\fRplugins\f[] \- Enable plugin processing (see \f[B]apex\-plugins\f[](7))
+
 .IP \(bu 2
-\f[CR]hardbreaks\f[R] \- Treat newlines as \f[CR]<br>\f[R]
+\fRcode\-line\-numbers\f[] \- Include line numbers in syntax\-highlighted code blocks
+
 .IP \(bu 2
-\f[CR]plugins\f[R] \- Enable plugin processing (see
-\f[B]apex\-plugins\f[R](7))
+\fRhighlight\-language\-only\f[] \- Only highlight code blocks that have a language specified
+
 .SS String options
-String keys take a free\-form string value (sometimes with a constrained
-set of options):
+
+.PP
+String keys take a free\-form string value (sometimes with a constrained set of options):
+
 .IP \(bu 2
-\f[CR]mode\f[R]
-.RS 2
+\fRmode\f[]
+
 .IP \(bu 2
-Values: \f[CR]commonmark\f[R], \f[CR]gfm\f[R],
-\f[CR]mmd\f[R]/\f[CR]multimarkdown\f[R], \f[CR]kramdown\f[R],
-\f[CR]unified\f[R]
-.RE
+Values: \fRcommonmark\f[], \fRgfm\f[], \fRmmd\f[]/\fRmultimarkdown\f[], \fRkramdown\f[], \fRunified\f[]
+
 .IP \(bu 2
-\f[CR]id\-format\f[R]
-.RS 2
+\fRid\-format\f[]
+
 .IP \(bu 2
-Values: \f[CR]gfm\f[R], \f[CR]mmd\f[R], \f[CR]kramdown\f[R]
-.RE
+Values: \fRgfm\f[], \fRmmd\f[], \fRkramdown\f[]
+
 .IP \(bu 2
-\f[CR]title\f[R]
-.RS 2
+\fRtitle\f[]
+
 .IP \(bu 2
 Document title (used especially in standalone mode)
-.RE
+
 .IP \(bu 2
-\f[CR]style\f[R] / \f[CR]css\f[R]
-.RS 2
+\fRstyle\f[] / \fRcss\f[]
+
 .IP \(bu 2
 Stylesheet path for standalone documents
-.RE
+
 .IP \(bu 2
-\f[CR]base\-dir\f[R]
-.RS 2
+\fRbase\-dir\f[]
+
 .IP \(bu 2
-Base directory used for resolving relative paths (images, includes,
-etc.)
-.RE
+Base directory used for resolving relative paths (images, includes, etc.)
+
 .IP \(bu 2
-\f[CR]bibliography\f[R]
-.RS 2
+\fRbibliography\f[]
+
 .IP \(bu 2
-Path to a bibliography file (\f[CR].bib\f[R], \f[CR].json\f[R],
-\f[CR].yml\f[R], \f[CR].yaml\f[R])
-.RE
+Path to a bibliography file (\fR.bib\f[], \fR.json\f[], \fR.yml\f[], \fR.yaml\f[])
+
 .IP \(bu 2
-\f[CR]csl\f[R]
-.RS 2
+\fRcsl\f[]
+
 .IP \(bu 2
 Path to a CSL style file
-.RE
+
 .IP \(bu 2
-\f[CR]language\f[R]
-.RS 2
+\fRlanguage\f[]
+
+.IP \(bu 2
+BCP 47 or similar language tag (e.g. \fRen\f[], \fRen\-US\f[], \fRfr\f[]); sets the HTML \fRlang\f[] attribute
+
+.IP \(bu 2
+\fRquoteslanguage\f[] / \fRQuotes Language\f[]
+
 .IP \(bu 2
-BCP 47 or similar language tag (e.g.\ \f[CR]en\f[R], \f[CR]en\-US\f[R],
-\f[CR]fr\f[R]); sets the HTML \f[CR]lang\f[R] attribute
-.RE
+Human\-readable language name used for quote styling (e.g. \fRenglish\f[], \fRfrench\f[], \fRgerman\f[])
+
 .IP \(bu 2
-\f[CR]quoteslanguage\f[R] / \f[CR]Quotes Language\f[R]
-.RS 2
+\fRcode\-highlight\f[]
+
 .IP \(bu 2
-Human\-readable language name used for quote styling
-(e.g.\ \f[CR]english\f[R], \f[CR]french\f[R], \f[CR]german\f[R])
-.RE
+External syntax highlighting tool: \fRpygments\f[] (or \fRp\f[]/\fRpyg\f[]), \fRskylighting\f[] (or \fRs\f[]/\fRsky\f[]), or \fRfalse\f[]/\fRnone\f[] to disable
+
 .PP
-You can also use arbitrary keys for your own templates and transforms;
-Apex simply passes them through to the metadata system so they can be
-referenced via \f[CR][%key]\f[R] and \f[CR][%key:transform]\f[R].
+You can also use arbitrary keys for your own templates and transforms; Apex simply passes them through to the metadata system so they can be referenced via \fR[%key]\f[] and \fR[%key:transform]\f[].
+
 .SH EXAMPLES
+
+.PP
 A typical setup might look like this:
-.IP "1." 3
-\f[B]Global defaults\f[R] in \f[CR]config.yml\f[R] for your overall
-writing style and locale.
-.IP "2." 3
-\f[B]Project config\f[R] via \f[CR]\-\-meta\-file project.yml\f[R] for
-bibliography and project\-specific settings.
-.IP "3." 3
-\f[B]Per\-document metadata\f[R] for title, author, and any exceptions
-to the defaults.
-.IP "4." 3
-Occasional \f[B]CLI overrides\f[R] for ad\-hoc one\-off changes
-(e.g.\ \f[CR]\-\-mode gfm\f[R] for a specific run).
+
+.IP "1." 4
+\f[B]Global defaults\f[] in \fRconfig.yml\f[] for your overall writing style and locale.
+
+.IP "2." 4
+\f[B]Project config\f[] via \fR\-\-meta\-file project.yml\f[] for bibliography and project\-specific settings.
+
+.IP "3." 4
+\f[B]Per\-document metadata\f[] for title, author, and any exceptions to the defaults.
+
+.IP "4." 4
+Occasional \f[B]CLI overrides\f[] for ad\-hoc one\-off changes (e.g. \fR\-\-mode gfm\f[] for a specific run).
+
 .PP
-Because all three configuration layers use the same metadata keys, you
-can gradually refine behavior without repeating yourself:
+Because all three configuration layers use the same metadata keys, you can gradually refine behavior without repeating yourself:
+
 .IP \(bu 2
-Put long\-lived, cross\-project settings in \f[CR]config.yml\f[R]
+Put long\-lived, cross\-project settings in \fRconfig.yml\f[]
+
 .IP \(bu 2
-Put project\-scoped settings in \f[CR]\-\-meta\-file\f[R] configs
+Put project\-scoped settings in \fR\-\-meta\-file\f[] configs
+
 .IP \(bu 2
 Put document\-specific settings in front matter
+
 .SH SEE ALSO
-\f[B]apex\f[R](1), \f[B]apex\-plugins\f[R](7)
+
+.PP
+\f[B]apex\f[](1), \f[B]apex\-plugins\f[](7)
+
 .PP
-For complete documentation, see the \c
-.UR https://github.com/ttscoff/apex/wiki
-Apex Wiki
-.UE \c
-\&.
+For complete documentation, see the Apex Wiki (https://github.com/ttscoff/apex/wiki).
+
 .SH AUTHOR
+
+.PP
 Brett Terpstra
+
 .SH COPYRIGHT
-Copyright (c) 2025 Brett Terpstra.
-Licensed under MIT License.
-.SH AUTHORS
-Brett Terpstra.
+
+.PP
+Copyright (c) 2025 Brett Terpstra. Licensed under MIT License.