[misc] some grinding on markdown/textinput

tstack · tstack · commit d2611bbe3a4f · 2025-03-11T16:31:22.000-07:00
diff --git a/src/internals/cmd-ref.rst b/src/internals/cmd-ref.rst
@@ -222,7 +222,7 @@
 :comment *text*
 ^^^^^^^^^^^^^^^
 
-  Attach a comment to the focused log line.  The comment will be displayed right below the log message it is associated with. The comment can be formatted using markdown and you can add new-lines with '\n'.
+  Attach a comment to the focused log line.  The comment will be displayed right below the log message it is associated with. The comment can contain Markdown directives for styling and linking.
 
   **Parameters**
     * **text\*** --- The comment text
diff --git a/src/lnav_commands.cc b/src/lnav_commands.cc
@@ -4142,9 +4142,8 @@ readline_context::command_t STD_COMMANDS[] = {
                           "comment will be "
                           "displayed right below the log message it is "
                           "associated with. "
-                          "The comment can be formatted using markdown and "
-                          "you can add "
-                          "new-lines with '\\n'.")
+                          "The comment can contain Markdown directives for "
+                          "styling and linking.")
             .with_parameter(
                 help_text("text", "The comment text")
                     .with_format(help_parameter_format_t::HPF_MULTILINE_TEXT))
diff --git a/src/textfile_highlighters.cc b/src/textfile_highlighters.cc
@@ -630,11 +630,33 @@ setup_highlights_int()
               .with_nestable(true)
               .with_text_format(text_format_t::TF_MARKDOWN)
               .with_role(role_t::VCR_LIST_GLYPH);
-    hm[{highlight_source_t::INTERNAL, "md.blockquote"}]
-        = highlighter(xpcre_compile(R"(^\s*(>\s+.*))"))
+    hm[{highlight_source_t::INTERNAL, "md.link"}]
+        = highlighter(xpcre_compile(R"((\[).+(\]\()[^\)]+(\)))"))
+              .with_nestable(true)
+              .with_text_format(text_format_t::TF_MARKDOWN)
+              .with_role(role_t::VCR_FOOTNOTE_BORDER);
+    hm[{highlight_source_t::INTERNAL, "md.directive"}]
+        = highlighter(
+              xpcre_compile(
+                  R"(^\s*>[ \t](\[!(?:NOTE|TIP|IMPORTANT|WARNING|CAUTION)\]))"))
               .with_nestable(true)
               .with_text_format(text_format_t::TF_MARKDOWN)
+              .with_role(role_t::VCR_DOC_DIRECTIVE);
+    hm[{highlight_source_t::INTERNAL, "md.blockquote"}]
+        = highlighter(xpcre_compile(R"(^\s*(>[ \t]+.*))"))
+              .with_nestable(false)
+              .with_text_format(text_format_t::TF_MARKDOWN)
               .with_role(role_t::VCR_QUOTED_TEXT);
+    hm[{highlight_source_t::INTERNAL, "md.table-hr"}]
+        = highlighter(xpcre_compile(R"((\|)?(:?-+:?)(\|))"))
+              .with_nestable(true)
+              .with_text_format(text_format_t::TF_MARKDOWN)
+              .with_role(role_t::VCR_DOC_DIRECTIVE);
+    hm[{highlight_source_t::INTERNAL, "md.table-row"}]
+        = highlighter(xpcre_compile(R"((\|)?(?:[^\\|]|\\.)+(\|))"))
+              .with_nestable(true)
+              .with_text_format(text_format_t::TF_MARKDOWN)
+              .with_role(role_t::VCR_DOC_DIRECTIVE);
     hm[{highlight_source_t::INTERNAL, "md.strikethrough"}]
         = highlighter(xpcre_compile(R"((?:^|\s+|\pP)(~[^~]+~)(?:$|\s+|\pP))"))
               .with_nestable(true)
diff --git a/src/textinput_curses.cc b/src/textinput_curses.cc
@@ -730,7 +730,7 @@ bool
 textinput_curses::handle_key(const ncinput& ch)
 {
     static const auto PREFIX_RE = lnav::pcre2pp::code::from_const(
-        R"(^\s*((?:-|\*|1\.)\s+(?:\[( |x|X)\]\s+)?)?)");
+        R"(^\s*((?:-|\*|1\.|>)\s+(?:\[( |x|X)\]\s+)?)?)");
     thread_local auto md = lnav::pcre2pp::match_data::unitialized();
 
     if (this->tc_notice) {
@@ -1229,7 +1229,9 @@ textinput_curses::handle_key(const ncinput& ch)
                                      .matches()
                                      .ignore_error();
 
-                if (match_opt && !match_opt->f_all.empty()) {
+                if (match_opt && !match_opt->f_all.empty()
+                    && match_opt->f_all.sf_end == this->tc_cursor.x)
+                {
                     if (md[1]) {
                         this->tc_selection = selected_range::from_key(
                             this->tc_cursor.copy_with_x(md[1]->sf_begin),
diff --git a/test/expected/test_cmds.sh_b6a3bb78e9d60e5e1f5ce5b18e40d2f1662707ab.out b/test/expected/test_cmds.sh_b6a3bb78e9d60e5e1f5ce5b18e40d2f1662707ab.out
@@ -837,8 +837,7 @@ For support questions, email:
 ══════════════════════════════════════════════════════════════════════
   Attach a comment to the focused log line.  The comment will be
   displayed right below the log message it is associated with. The
-  comment can be formatted using markdown and you can add new-lines
-  with '\n'.
+  comment can contain Markdown directives for styling and linking.
 [4mParameter[0m
   [4mtext[0m   The comment text
 [4mSee Also[0m
diff --git a/test/expected/test_text_file.sh_08d527b6655b80eb3fc9f19d502b08ce28d71c80.out b/test/expected/test_text_file.sh_08d527b6655b80eb3fc9f19d502b08ce28d71c80.out
@@ -1,14 +1,14 @@
 [32m<!-- This is a comment for testing purposes -->[0m
 
-[![Build](https://github.com/tstack/lnav/workflows/ci-build/badge.svg)](https://github.com/tstack/lnav/actions?[4mquery[0m=workflow%3Aci-build)
-[![Docs](https://readthedocs.org/projects/lnav/badge/?[4mversion[0m=latest&[4mstyle[0m=plastic)](https://docs.lnav.org)
-[![Coverage Status](https://coveralls.io/repos/github/tstack/lnav/badge.svg?[4mbranch[0m=master)](https://coveralls.io/github/tstack/lnav?[4mbranch[0m=master)
-[![lnav](https://snapcraft.io/lnav/badge.svg)](https://snapcraft.io/lnav)
-[![Gurubase](https://img.shields.io/badge/Gurubase-Ask%20LNAV%20Guru-006BFF)](https://gurubase.io/g/lnav)
+[34m[[0m![Build](https://github.com/tstack/lnav/workflows/ci-build/badge.svg)[34m]([0mhttps://github.com/tstack/lnav/actions?[4mquery[0m=workflow%3Aci-build[34m)[0m
+[34m[[0m![Docs](https://readthedocs.org/projects/lnav/badge/?[4mversion[0m=latest&[4mstyle[0m=plastic)[34m]([0mhttps://docs.lnav.org[34m)[0m
+[34m[[0m![Coverage Status](https://coveralls.io/repos/github/tstack/lnav/badge.svg?[4mbranch[0m=master)[34m]([0mhttps://coveralls.io/github/tstack/lnav?[4mbranch[0m=master[34m)[0m
+[34m[[0m![lnav](https://snapcraft.io/lnav/badge.svg)[34m]([0mhttps://snapcraft.io/lnav[34m)[0m
+[34m[[0m![Gurubase](https://img.shields.io/badge/Gurubase-Ask%20LNAV%20Guru-006BFF)[34m]([0mhttps://gurubase.io/g/lnav[34m)[0m
 
-[<img [4msrc[0m=[35m"https://assets-global.website-files.com/6257adef93867e50d84d30e2/62594fddd654fc29fcc07359_cb48d2a8d4991281d7a6a95d2f58195e.svg"[0m [4mheight[0m=[35m"20"[0m [4malt[0m=[35m"Discord Logo"[0m/>](https://discord.gg/erBPnKwz7R)
+[34m[[0m<img [4msrc[0m=[35m"https://assets-global.website-files.com/6257adef93867e50d84d30e2/62594fddd654fc29fcc07359_cb48d2a8d4991281d7a6a95d2f58195e.svg"[0m [4mheight[0m=[35m"20"[0m [4malt[0m=[35m"Discord Logo"[0m/>[34m]([0mhttps://discord.gg/erBPnKwz7R[34m)[0m
 
-[4m_This is the source repository for [0m[1m[4m**lnav**[0m[4m, visit [https://lnav.org](https://lnav.org) for a high level overview._[0m
+[4m_This is the source repository for [0m[1m[4m**lnav**[0m[4m, visit [0m[4m[34m[[0m[4mhttps://lnav.org[0m[4m[34m]([0m[4mhttps://lnav.org[0m[4m[34m)[0m[4m for a high level overview._[0m
 
 [1m[35m# LNAV -- The Logfile Navigator[0m
 
@@ -20,25 +20,25 @@ set of files/directories, [1m**lnav**[0m will:
 [33m-[0m merge the files by time into a single view;
 [33m-[0m tail the files, follow renames, find new files in directories;
 [33m-[0m build an index of errors and warnings;
-[33m-[0m [pretty-print JSON-lines](https://docs.lnav.org/en/latest/formats.html#json-lines).
+[33m-[0m [34m[[0mpretty-print JSON-lines[34m]([0mhttps://docs.lnav.org/en/latest/formats.html#json-lines[34m)[0m.
 
 Then, in the [1m**lnav**[0m TUI, you can:
 
-[33m-[0m jump quickly to the previous/next error ([press [35m`e`[0m/[35m`E`[0m](https://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation));
-[33m-[0m search using regular expressions ([press [35m`/`[0m](https://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation));
-[33m-[0m highlight text with a regular expression ([[35m`:highlight`[0m](https://docs.lnav.org/en/latest/commands.html#highlight-pattern) command);
-[33m-[0m filter messages using [regular expressions](https://docs.lnav.org/en/latest/usage.html#regular-expression-match) or [SQLite expressions](https://docs.lnav.org/en/latest/usage.html#sqlite-expression);
-[33m-[0m pretty-print structured text ([press [35m`P`[0m](https://docs.lnav.org/en/latest/ui.html#pretty));
-[33m-[0m view a histogram of messages over time ([press [35m`i`[0m](https://docs.lnav.org/en/latest/ui.html#hist));
-[33m-[0m analyze messages using SQLite ([press [35m`;`[0m](https://docs.lnav.org/en/latest/sqlext.html))
+[33m-[0m jump quickly to the previous/next error ([34m[[0mpress [35m`e`[0m/[35m`E`[0m[34m]([0mhttps://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation[34m)[0m);
+[33m-[0m search using regular expressions ([34m[[0mpress [35m`/`[0m[34m]([0mhttps://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation[34m)[0m);
+[33m-[0m highlight text with a regular expression ([34m[[0m[35m`:highlight`[0m[34m]([0mhttps://docs.lnav.org/en/latest/commands.html#highlight-pattern[34m)[0m command);
+[33m-[0m filter messages using [34m[[0mregular expressions](https://docs.lnav.org/en/latest/usage.html#regular-expression-match) or [SQLite expressions[34m]([0mhttps://docs.lnav.org/en/latest/usage.html#sqlite-expression[34m)[0m;
+[33m-[0m pretty-print structured text ([34m[[0mpress [35m`P`[0m[34m]([0mhttps://docs.lnav.org/en/latest/ui.html#pretty[34m)[0m);
+[33m-[0m view a histogram of messages over time ([34m[[0mpress [35m`i`[0m[34m]([0mhttps://docs.lnav.org/en/latest/ui.html#hist[34m)[0m);
+[33m-[0m analyze messages using SQLite ([34m[[0mpress [35m`;`[0m[34m]([0mhttps://docs.lnav.org/en/latest/sqlext.html[34m)[0m)
 
 [1m## Screenshot[0m
 
 The following screenshot shows a mix of syslog and web access log
 files.  Failed requests are shown in red.  Identifiers, like IP
 address and PIDs are semantically highlighted.
 
-[![Screenshot](docs/assets/images/lnav-front-page.png)](docs/assets/images/lnav-front-page.png)
+[34m[[0m![Screenshot](docs/assets/images/lnav-front-page.png)[34m]([0mdocs/assets/images/lnav-front-page.png[34m)[0m
 
 [1m## Why not [0m[1m**just**[0m[1m use [0m[1m[35m`tail`[0m[1m/[0m[1m[35m`grep`[0m[1m/[0m[1m[35m`less`[0m[1m?[0m
 
@@ -57,16 +57,16 @@ You can SSH into a demo node to play with lnav before installing.
 The [35m"playground"[0m account starts lnav with a couple of log files as
 an example:
 
-[[35m`$ ssh playground@demo.lnav.org`[0m](ssh://playground@demo.lnav.org)
+[34m[[0m[35m`$ ssh playground@demo.lnav.org`[0m[34m]([0mssh://playground@demo.lnav.org[34m)[0m
 
 The [35m"tutorial 1"[0m account is an interactive tutorial that can teach 
 you the basics of operation:
 
-[[35m`$ ssh tutorial1@demo.lnav.org`[0m](ssh://tutorial1@demo.lnav.org)
+[34m[[0m[35m`$ ssh tutorial1@demo.lnav.org`[0m[34m]([0mssh://tutorial1@demo.lnav.org[34m)[0m
 
 [1m## Installation[0m
 
-[Download a statically-linked binary for Linux/MacOS from the release page](https://github.com/tstack/lnav/releases/latest#release-artifacts)
+[34m[[0mDownload a statically-linked binary for Linux/MacOS from the release page[34m]([0mhttps://github.com/tstack/lnav/releases/latest#release-artifacts[34m)[0m
 
 [4m### Brew on MacOS[0m
 
@@ -90,7 +90,7 @@ the log messages that were recognized[^1]. You can then use the
 usual hotkeys to move around the view (arrow keys or
 [35m`j`[0m/[35m`k`[0m/[35m`h`[0m/[35m`l`[0m to move down/up/left/right).
 
-See the [Usage section](https://docs.lnav.org/en/latest/usage.html)
+See the [34m[[0mUsage section[34m]([0mhttps://docs.lnav.org/en/latest/usage.html[34m)[0m
 of the online documentation for more information.
 
 [^1]: Files that do not contain log messages can be seen in the 
@@ -101,28 +101,28 @@ of the online documentation for more information.
 On systems running [35m`systemd-journald`[0m, you can use [35m`lnav`[0m as the pager:
 
 [35m```[0m
-[35m$ journalctl | lnav[0m
+[35m$ journalctl [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 or in follow mode:
 
 [35m```[0m
-[35m$ journalctl -f | lnav[0m
+[35m$ journalctl -f [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 Since [35m`journalctl`[0m's default output format omits the year, if you are
 viewing logs which span multiple years you will need to change the
 output format to include the year, otherwise [35m`lnav`[0m gets confused:
 
 [35m```[0m
-[35m$ journalctl -o short-iso | lnav[0m
+[35m$ journalctl -o short-iso [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 It is also possible to use [35m`journalctl`[0m's json output format and [35m`lnav`[0m
 will make use of additional fields such as PRIORITY and \_SYSTEMD_UNIT:
 
 [35m```[0m
-[35m$ journalctl -o json | lnav[0m
+[35m$ journalctl -o json [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 In case some MESSAGE fields contain special characters such as
@@ -131,14 +131,14 @@ specifying [35m`journalctl`[0m's [35m`-a`[0m option might be preferable in o
 to output those messages still in a non-binary representation:
 
 [35m```[0m
-[35m$ journalctl -a -o json | lnav[0m
+[35m$ journalctl -a -o json [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 If using systemd v236 or newer, the output fields can be limited to
 the ones actually recognized by [35m`lnav`[0m for increased efficiency:
 
 [35m```[0m
-[35m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT | lnav[0m
+[35m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 
 If your system has been running for a long time, for increased
@@ -153,19 +153,19 @@ of log lines fed into [35m`lnav`[0m via [35m`journalctl`[0m's [35m`-b`[0m
 Please file issues on this repository or use the discussions section.
 The following alternatives are also available:
 
-[33m-[0m [support@lnav.org](mailto:support@lnav.org)
-[33m-[0m [Discord](https://discord.gg/erBPnKwz7R)
-[33m-[0m [Google Groups](https://groups.google.com/g/lnav)
+[33m-[0m [34m[[0msupport@lnav.org[34m]([0mmailto:support@lnav.org[34m)[0m
+[33m-[0m [34m[[0mDiscord[34m]([0mhttps://discord.gg/erBPnKwz7R[34m)[0m
+[33m-[0m [34m[[0mGoogle Groups[34m]([0mhttps://groups.google.com/g/lnav[34m)[0m
 
 [1m## Links[0m
 
-[33m-[0m [Main Site](https://lnav.org)
-[33m-[0m [[1m**Documentation**[0m](https://docs.lnav.org) on Read the Docs
-[33m-[0m [Internal Architecture](ARCHITECTURE.md)
+[33m-[0m [34m[[0mMain Site[34m]([0mhttps://lnav.org[34m)[0m
+[33m-[0m [34m[[0m[1m**Documentation**[0m[34m]([0mhttps://docs.lnav.org[34m)[0m on Read the Docs
+[33m-[0m [34m[[0mInternal Architecture[34m]([0mARCHITECTURE.md[34m)[0m
 
 [1m## Contributing[0m
 
-[33m-[0m [Become a Sponsor on GitHub](https://github.com/sponsors/tstack)
+[33m-[0m [34m[[0mBecome a Sponsor on GitHub[34m]([0mhttps://github.com/sponsors/tstack[34m)[0m
 
 [4m### Building From Source[0m
 
@@ -199,5 +199,5 @@ Run [35m`./autogen.sh`[0m if compiling from a cloned repository.
 
 [1m## See Also[0m
 
-[Angle-grinder](https://github.com/rcoh/angle-grinder) is a tool to slice and dice log files on the command-line.
+[34m[[0mAngle-grinder[34m]([0mhttps://github.com/rcoh/angle-grinder[34m)[0m is a tool to slice and dice log files on the command-line.
 If you're familiar with the SumoLogic query language, you might find this tool more comfortable to work with.
diff --git a/test/expected/test_text_file.sh_49e04528d748c7982cec2a7e2853462a0c74bcb1.out b/test/expected/test_text_file.sh_49e04528d748c7982cec2a7e2853462a0c74bcb1.out
@@ -4,10 +4,10 @@
 
 [1m[35m# Table of Contents[0m
 
-[33m-[0m [Table of Contents](#table-of-contents)
-    [33m-[0m [Test](#test)
-    [33m-[0m [Github Alerts](#github-alerts)
-    [33m-[0m [Table](#table)
+[33m-[0m [34m[[0mTable of Contents[34m]([0m#table-of-contents[34m)[0m
+    [33m-[0m [34m[[0mTest[34m]([0m#test[34m)[0m
+    [33m-[0m [34m[[0mGithub Alerts[34m]([0m#github-alerts[34m)[0m
+    [33m-[0m [34m[[0mTable[34m]([0m#table[34m)[0m
 
 [1m## Test[0m
 
diff --git a/test/expected/test_text_file.sh_5b51b55dff7332c5bee2c9b797c401c5614d574a.out b/test/expected/test_text_file.sh_5b51b55dff7332c5bee2c9b797c401c5614d574a.out
@@ -134,35 +134,35 @@ view (reachable by pressing [37m[40m t [0m).
 On systems running [37m[40m systemd-journald [0m, you can use [37m[40m lnav [0m as the
 pager:
 
- ▌[37m[40m$ journalctl | lnav                     [0m
+ ▌[37m[40m$ journalctl [0m[37m[40m|[0m[37m[40m lnav                     [0m
 
 or in follow mode:
 
- ▌[37m[40m$ journalctl -f | lnav                  [0m
+ ▌[37m[40m$ journalctl -f [0m[37m[40m|[0m[37m[40m lnav                  [0m
 
 Since [37m[40m journalctl [0m's default output format omits the year, if you are
 viewing logs which span multiple years you will need to change the
 output format to include the year, otherwise [37m[40m lnav [0m gets confused:
 
- ▌[37m[40m$ journalctl -o short-iso | lnav        [0m
+ ▌[37m[40m$ journalctl -o short-iso [0m[37m[40m|[0m[37m[40m lnav        [0m
 
 It is also possible to use [37m[40m journalctl [0m's json output format and
 [37m[40m lnav [0mwill make use of additional fields such as PRIORITY and
 _SYSTEMD_UNIT:
 
- ▌[37m[40m$ journalctl -o json | lnav             [0m
+ ▌[37m[40m$ journalctl -o json [0m[37m[40m|[0m[37m[40m lnav             [0m
 
 In case some MESSAGE fields contain special characters such as ANSI
 color codes which are considered as unprintable by journalctl,
 specifying [37m[40m journalctl [0m's [37m[40m -a [0m option might be preferable in order to
 output those messages still in a non-binary representation:
 
- ▌[37m[40m$ journalctl -a -o json | lnav          [0m
+ ▌[37m[40m$ journalctl -a -o json [0m[37m[40m|[0m[37m[40m lnav          [0m
 
 If using systemd v236 or newer, the output fields can be limited to
 the ones actually recognized by [37m[40m lnav [0m for increased efficiency:
 
- ▌[37m[40m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT | lnav    [0m
+ ▌[37m[40m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT [0m[37m[40m|[0m[37m[40m lnav    [0m
 
 If your system has been running for a long time, for increased
 efficiency you may want to limit the number of log lines fed into
diff --git a/test/expected/test_text_file.sh_6a24078983cf1b7a80b6fb65d5186cd125498136.out b/test/expected/test_text_file.sh_6a24078983cf1b7a80b6fb65d5186cd125498136.out
diff --git a/test/expected/test_text_file.sh_ac872aadda29b9a824361a2c711d62ec1c75d40f.out b/test/expected/test_text_file.sh_ac872aadda29b9a824361a2c711d62ec1c75d40f.out
diff --git a/test/expected/test_text_file.sh_e088ea61a5382458cc48a2607e2639e52b0be1da.out b/test/expected/test_text_file.sh_e088ea61a5382458cc48a2607e2639e52b0be1da.out

-Original file line number
+Diff line change
@@ @@ -1,14 +1,14 @@ @@
 [32m<!-- This is a comment for testing purposes -->[0m
 -[![Build](https://github.com/tstack/lnav/workflows/ci-build/badge.svg)](https://github.com/tstack/lnav/actions?[4mquery[0m=workflow%3Aci-build)
 -[![Docs](https://readthedocs.org/projects/lnav/badge/?[4mversion[0m=latest&[4mstyle[0m=plastic)](https://docs.lnav.org)
 -[![Coverage Status](https://coveralls.io/repos/github/tstack/lnav/badge.svg?[4mbranch[0m=master)](https://coveralls.io/github/tstack/lnav?[4mbranch[0m=master)
 -[![lnav](https://snapcraft.io/lnav/badge.svg)](https://snapcraft.io/lnav)
 -[![Gurubase](https://img.shields.io/badge/Gurubase-Ask%20LNAV%20Guru-006BFF)](https://gurubase.io/g/lnav)
 +[34m[[0m![Build](https://github.com/tstack/lnav/workflows/ci-build/badge.svg)[34m]([0mhttps://github.com/tstack/lnav/actions?[4mquery[0m=workflow%3Aci-build[34m)[0m
 +[34m[[0m![Docs](https://readthedocs.org/projects/lnav/badge/?[4mversion[0m=latest&[4mstyle[0m=plastic)[34m]([0mhttps://docs.lnav.org[34m)[0m
 +[34m[[0m![Coverage Status](https://coveralls.io/repos/github/tstack/lnav/badge.svg?[4mbranch[0m=master)[34m]([0mhttps://coveralls.io/github/tstack/lnav?[4mbranch[0m=master[34m)[0m
 +[34m[[0m![lnav](https://snapcraft.io/lnav/badge.svg)[34m]([0mhttps://snapcraft.io/lnav[34m)[0m
 +[34m[[0m![Gurubase](https://img.shields.io/badge/Gurubase-Ask%20LNAV%20Guru-006BFF)[34m]([0mhttps://gurubase.io/g/lnav[34m)[0m
 -[<img [4msrc[0m=[35m"https://assets-global.website-files.com/6257adef93867e50d84d30e2/62594fddd654fc29fcc07359_cb48d2a8d4991281d7a6a95d2f58195e.svg"[0m [4mheight[0m=[35m"20"[0m [4malt[0m=[35m"Discord Logo"[0m/>](https://discord.gg/erBPnKwz7R)
 +[34m[[0m<img [4msrc[0m=[35m"https://assets-global.website-files.com/6257adef93867e50d84d30e2/62594fddd654fc29fcc07359_cb48d2a8d4991281d7a6a95d2f58195e.svg"[0m [4mheight[0m=[35m"20"[0m [4malt[0m=[35m"Discord Logo"[0m/>[34m]([0mhttps://discord.gg/erBPnKwz7R[34m)[0m
 -[4m_This is the source repository for [0m[1m[4m**lnav**[0m[4m, visit [https://lnav.org](https://lnav.org) for a high level overview._[0m
 +[4m_This is the source repository for [0m[1m[4m**lnav**[0m[4m, visit [0m[4m[34m[[0m[4mhttps://lnav.org[0m[4m[34m]([0m[4mhttps://lnav.org[0m[4m[34m)[0m[4m for a high level overview._[0m
 [1m[35m# LNAV -- The Logfile Navigator[0m
 [33m-[0m merge the files by time into a single view;
 [33m-[0m tail the files, follow renames, find new files in directories;
 [33m-[0m build an index of errors and warnings;
 -[33m-[0m [pretty-print JSON-lines](https://docs.lnav.org/en/latest/formats.html#json-lines).
 +[33m-[0m [34m[[0mpretty-print JSON-lines[34m]([0mhttps://docs.lnav.org/en/latest/formats.html#json-lines[34m)[0m.
 Then, in the [1m**lnav**[0m TUI, you can:
 -[33m-[0m jump quickly to the previous/next error ([press [35m`e`[0m/[35m`E`[0m](https://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation));
 -[33m-[0m search using regular expressions ([press [35m`/`[0m](https://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation));
 -[33m-[0m highlight text with a regular expression ([[35m`:highlight`[0m](https://docs.lnav.org/en/latest/commands.html#highlight-pattern) command);
 -[33m-[0m filter messages using [regular expressions](https://docs.lnav.org/en/latest/usage.html#regular-expression-match) or [SQLite expressions](https://docs.lnav.org/en/latest/usage.html#sqlite-expression);
 -[33m-[0m pretty-print structured text ([press [35m`P`[0m](https://docs.lnav.org/en/latest/ui.html#pretty));
 -[33m-[0m view a histogram of messages over time ([press [35m`i`[0m](https://docs.lnav.org/en/latest/ui.html#hist));
 -[33m-[0m analyze messages using SQLite ([press [35m`;`[0m](https://docs.lnav.org/en/latest/sqlext.html))
 +[33m-[0m jump quickly to the previous/next error ([34m[[0mpress [35m`e`[0m/[35m`E`[0m[34m]([0mhttps://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation[34m)[0m);
 +[33m-[0m search using regular expressions ([34m[[0mpress [35m`/`[0m[34m]([0mhttps://docs.lnav.org/en/latest/hotkeys.html#spatial-navigation[34m)[0m);
 +[33m-[0m highlight text with a regular expression ([34m[[0m[35m`:highlight`[0m[34m]([0mhttps://docs.lnav.org/en/latest/commands.html#highlight-pattern[34m)[0m command);
 +[33m-[0m filter messages using [34m[[0mregular expressions](https://docs.lnav.org/en/latest/usage.html#regular-expression-match) or [SQLite expressions[34m]([0mhttps://docs.lnav.org/en/latest/usage.html#sqlite-expression[34m)[0m;
 +[33m-[0m pretty-print structured text ([34m[[0mpress [35m`P`[0m[34m]([0mhttps://docs.lnav.org/en/latest/ui.html#pretty[34m)[0m);
 +[33m-[0m view a histogram of messages over time ([34m[[0mpress [35m`i`[0m[34m]([0mhttps://docs.lnav.org/en/latest/ui.html#hist[34m)[0m);
 +[33m-[0m analyze messages using SQLite ([34m[[0mpress [35m`;`[0m[34m]([0mhttps://docs.lnav.org/en/latest/sqlext.html[34m)[0m)
 [1m## Screenshot[0m
 The following screenshot shows a mix of syslog and web access log
 files.  Failed requests are shown in red.  Identifiers, like IP
 address and PIDs are semantically highlighted.
 -[![Screenshot](docs/assets/images/lnav-front-page.png)](docs/assets/images/lnav-front-page.png)
 +[34m[[0m![Screenshot](docs/assets/images/lnav-front-page.png)[34m]([0mdocs/assets/images/lnav-front-page.png[34m)[0m
 [1m## Why not [0m[1m**just**[0m[1m use [0m[1m[35m`tail`[0m[1m/[0m[1m[35m`grep`[0m[1m/[0m[1m[35m`less`[0m[1m?[0m
 The [35m"playground"[0m account starts lnav with a couple of log files as
 an example:
 -[[35m`$ ssh playground@demo.lnav.org`[0m](ssh://playground@demo.lnav.org)
 +[34m[[0m[35m`$ ssh playground@demo.lnav.org`[0m[34m]([0mssh://playground@demo.lnav.org[34m)[0m
 The [35m"tutorial 1"[0m account is an interactive tutorial that can teach
 you the basics of operation:
 -[[35m`$ ssh tutorial1@demo.lnav.org`[0m](ssh://tutorial1@demo.lnav.org)
 +[34m[[0m[35m`$ ssh tutorial1@demo.lnav.org`[0m[34m]([0mssh://tutorial1@demo.lnav.org[34m)[0m
 [1m## Installation[0m
 -[Download a statically-linked binary for Linux/MacOS from the release page](https://github.com/tstack/lnav/releases/latest#release-artifacts)
 +[34m[[0mDownload a statically-linked binary for Linux/MacOS from the release page[34m]([0mhttps://github.com/tstack/lnav/releases/latest#release-artifacts[34m)[0m
 [4m### Brew on MacOS[0m
 usual hotkeys to move around the view (arrow keys or
 [35m`j`[0m/[35m`k`[0m/[35m`h`[0m/[35m`l`[0m to move down/up/left/right).
 -See the [Usage section](https://docs.lnav.org/en/latest/usage.html)
 +See the [34m[[0mUsage section[34m]([0mhttps://docs.lnav.org/en/latest/usage.html[34m)[0m
 of the online documentation for more information.
 [^1]: Files that do not contain log messages can be seen in the
 On systems running [35m`systemd-journald`[0m, you can use [35m`lnav`[0m as the pager:
 [35m```[0m
 -[35m$ journalctl | lnav[0m
 +[35m$ journalctl [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 or in follow mode:
 [35m```[0m
 -[35m$ journalctl -f | lnav[0m
 +[35m$ journalctl -f [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 Since [35m`journalctl`[0m's default output format omits the year, if you are
 viewing logs which span multiple years you will need to change the
 output format to include the year, otherwise [35m`lnav`[0m gets confused:
 [35m```[0m
 -[35m$ journalctl -o short-iso | lnav[0m
 +[35m$ journalctl -o short-iso [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 It is also possible to use [35m`journalctl`[0m's json output format and [35m`lnav`[0m
 will make use of additional fields such as PRIORITY and \_SYSTEMD_UNIT:
 [35m```[0m
 -[35m$ journalctl -o json | lnav[0m
 +[35m$ journalctl -o json [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 In case some MESSAGE fields contain special characters such as
 to output those messages still in a non-binary representation:
 [35m```[0m
 -[35m$ journalctl -a -o json | lnav[0m
 +[35m$ journalctl -a -o json [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 If using systemd v236 or newer, the output fields can be limited to
 the ones actually recognized by [35m`lnav`[0m for increased efficiency:
 [35m```[0m
 -[35m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT | lnav[0m
 +[35m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT [0m[35m|[0m[35m lnav[0m
 [35m```[0m
 If your system has been running for a long time, for increased
 Please file issues on this repository or use the discussions section.
 The following alternatives are also available:
 -[33m-[0m [support@lnav.org](mailto:support@lnav.org)
 -[33m-[0m [Discord](https://discord.gg/erBPnKwz7R)
 -[33m-[0m [Google Groups](https://groups.google.com/g/lnav)
 +[33m-[0m [34m[[0msupport@lnav.org[34m]([0mmailto:support@lnav.org[34m)[0m
 +[33m-[0m [34m[[0mDiscord[34m]([0mhttps://discord.gg/erBPnKwz7R[34m)[0m
 +[33m-[0m [34m[[0mGoogle Groups[34m]([0mhttps://groups.google.com/g/lnav[34m)[0m
 [1m## Links[0m
 -[33m-[0m [Main Site](https://lnav.org)
 -[33m-[0m [[1m**Documentation**[0m](https://docs.lnav.org) on Read the Docs
 -[33m-[0m [Internal Architecture](ARCHITECTURE.md)
 +[33m-[0m [34m[[0mMain Site[34m]([0mhttps://lnav.org[34m)[0m
 +[33m-[0m [34m[[0m[1m**Documentation**[0m[34m]([0mhttps://docs.lnav.org[34m)[0m on Read the Docs
 +[33m-[0m [34m[[0mInternal Architecture[34m]([0mARCHITECTURE.md[34m)[0m
 [1m## Contributing[0m
 -[33m-[0m [Become a Sponsor on GitHub](https://github.com/sponsors/tstack)
 +[33m-[0m [34m[[0mBecome a Sponsor on GitHub[34m]([0mhttps://github.com/sponsors/tstack[34m)[0m
 [4m### Building From Source[0m
 [1m## See Also[0m
 -[Angle-grinder](https://github.com/rcoh/angle-grinder) is a tool to slice and dice log files on the command-line.
 +[34m[[0mAngle-grinder[34m]([0mhttps://github.com/rcoh/angle-grinder[34m)[0m is a tool to slice and dice log files on the command-line.
 If you're familiar with the SumoLogic query language, you might find this tool more comfortable to work with.
-Original file line number
+Diff line change
 [1m[35m# Table of Contents[0m
 -[33m-[0m [Table of Contents](#table-of-contents)
 -    [33m-[0m [Test](#test)
 -    [33m-[0m [Github Alerts](#github-alerts)
 -    [33m-[0m [Table](#table)
 +[33m-[0m [34m[[0mTable of Contents[34m]([0m#table-of-contents[34m)[0m
 +    [33m-[0m [34m[[0mTest[34m]([0m#test[34m)[0m
 +    [33m-[0m [34m[[0mGithub Alerts[34m]([0m#github-alerts[34m)[0m
 +    [33m-[0m [34m[[0mTable[34m]([0m#table[34m)[0m
 [1m## Test[0m
-Original file line number
+Diff line change
 On systems running [37m[40m systemd-journald [0m, you can use [37m[40m lnav [0m as the
 pager:
 - ▌[37m[40m$ journalctl | lnav                     [0m
 + ▌[37m[40m$ journalctl [0m[37m[40m|[0m[37m[40m lnav                     [0m
 or in follow mode:
 - ▌[37m[40m$ journalctl -f | lnav                  [0m
 + ▌[37m[40m$ journalctl -f [0m[37m[40m|[0m[37m[40m lnav                  [0m
 Since [37m[40m journalctl [0m's default output format omits the year, if you are
 viewing logs which span multiple years you will need to change the
 output format to include the year, otherwise [37m[40m lnav [0m gets confused:
 - ▌[37m[40m$ journalctl -o short-iso | lnav        [0m
 + ▌[37m[40m$ journalctl -o short-iso [0m[37m[40m|[0m[37m[40m lnav        [0m
 It is also possible to use [37m[40m journalctl [0m's json output format and
 [37m[40m lnav [0mwill make use of additional fields such as PRIORITY and
 _SYSTEMD_UNIT:
 - ▌[37m[40m$ journalctl -o json | lnav             [0m
 + ▌[37m[40m$ journalctl -o json [0m[37m[40m|[0m[37m[40m lnav             [0m
 In case some MESSAGE fields contain special characters such as ANSI
 color codes which are considered as unprintable by journalctl,
 specifying [37m[40m journalctl [0m's [37m[40m -a [0m option might be preferable in order to
 output those messages still in a non-binary representation:
 - ▌[37m[40m$ journalctl -a -o json | lnav          [0m
 + ▌[37m[40m$ journalctl -a -o json [0m[37m[40m|[0m[37m[40m lnav          [0m
 If using systemd v236 or newer, the output fields can be limited to
 the ones actually recognized by [37m[40m lnav [0m for increased efficiency:
 - ▌[37m[40m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT | lnav    [0m
 + ▌[37m[40m$ journalctl -o json --output-fields=MESSAGE,PRIORITY,_PID,SYSLOG_IDENTIFIER,_SYSTEMD_UNIT [0m[37m[40m|[0m[37m[40m lnav    [0m
 If your system has been running for a long time, for increased
 efficiency you may want to limit the number of log lines fed into