help topics no longer need to be unique and can be toggled through with the `?$` command.

* This mirrors how the `FT$` command toggles through several results.
* Some non-unique .SCITECO_TOPICs have been added to sciteco(1) and sciteco(7).
* This works by inserting non-unique keys into the help topic RB tree - or rather
  by turning filename:pos also into keys since rb3ptr does not allow non-unique keys.
  When searching for a topic, we sort lower than any other entry with the same name.
  This way we can easily iterate all entries with the same name (search topic).
  The alternative would have been to maintain a linked list in each and every
  teco_help_topic_t.
* teco_rb3str_auto_complete() now filters out possible duplicate keys.
* Updated test case: check for non-unique topic names.

2 files changed, 11 insertions, 10 deletions

diff --git a/doc/sciteco.1.in b/doc/sciteco.1.in
index 1e7fe3b..dc10f11 100644
--- a/doc/sciteco.1.in
+++ b/doc/sciteco.1.in
@@ -191,7 +191,7 @@ option.
 .SCITECO_TOPIC "-h" "--help"
 Display a short help text on the console.
 .IP "\fB-v\fR, \fB--version\fR"
-.SCITECO_TOPIC "-v" "--version"
+.SCITECO_TOPIC "-v" "--version" version
 Display the \*(ST version in an easy to parse way.
 See also the \fBEO\fP command.
 .IP "\fB-q\fR, \fB--quiet\fR"
@@ -367,7 +367,7 @@ environment before initializing Curses, so these variables
 can be modified in the profile macro.
 .
 .LP
-.SCITECO_TOPIC "$SCITECO_CLIPBOARD_SET" "$SCITECO_CLIPBOARD_GET"
+.SCITECO_TOPIC "$SCITECO_CLIPBOARD_SET" "$SCITECO_CLIPBOARD_GET" clipboard
 On ncurses, in addition to the OSC-52 protocol, you can use external
 processes to drive the built-in clipboard Q-Registers (\(lq~\(rq and so on).
 For that you can set the \fBSCITECO_CLIPBOARD_SET\fP and \fBSCITECO_CLIPBOARD_GET\fP
@@ -391,7 +391,7 @@ for an example of how to integrate the X11 clipboard via
 Integrating with Wayland and the Mac OS clipboards is of course also possible.
 .
 .LP
-.SCITECO_TOPIC "$SCITECO_LSP" "$SCITECO_LSP_ROOT"
+.SCITECO_TOPIC "$SCITECO_LSP" "$SCITECO_LSP_ROOT" LSP
 The \fBSCITECO_LSP\fP environment variable must be set to a language
 server command line if you would like to use the \fBFT\fP command for looking up
 symbols, definitions or references.
diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template
index 4b6987a..0ff3f51 100644
--- a/doc/sciteco.7.template
+++ b/doc/sciteco.7.template
@@ -1604,6 +1604,7 @@ Its integer part is unused.
 It is initialized automatically on startup.
 .TP
 .BI $ variable
+.SCITECO_TOPIC environment
 Global Q-Registers beginning with a dollar sign that
 do not contain any \(lq=\(rq represent the process environment
 (the environment variables).
@@ -1692,7 +1693,7 @@ the original clipboard contents, though.
 The numeric parts of the clipboard registers are
 currently not used by \*(ST.
 .TP
-.SCITECO_TOPIC ^Ax
+.SCITECO_TOPIC ^Ax argv arguments
 .BI ^A x
 An argument passed on the operating system's command line.
 \fIx\fP can be an integer beginning with 0.
@@ -1858,7 +1859,7 @@ character and their case is insignificant.
 In the following list of supported expressions, the caret-notation
 thus refers to the corresponding control code:
 .TP
-.SCITECO_TOPIC ^P
+.SCITECO_TOPIC ^P verbatim
 .B ^P
 Disable interpretation of all further string building characters,
 so all following characters will be taken verbatim.
@@ -1885,7 +1886,7 @@ When \fB^V\fP is not followed by \fB^V\fP, a single character
 \fIc\fP is lower-cased.
 \# Which is pretty pointless nowadays.
 .TP
-.SCITECO_TOPIC ^W^W ^Wc
+.SCITECO_TOPIC ^W^W ^Wc upper
 .B ^W^W
 .TQ
 .BI ^W c
@@ -2258,7 +2259,7 @@ In addition to labels and unlike most classic TECO dialects,
 \*(ST also supports true comments.
 True comments are parsed faster than labels and do not
 take up memory in goto tables.
-.SCITECO_TOPIC "!*" "block comment"
+.SCITECO_TOPIC "!*" comment
 One form of comments is the block comment:
 .br
 .BI !* comment *!
@@ -2271,7 +2272,7 @@ They are analoguous to C's
 comments.
 .LP
 \# This form of comment was originally in TECO-64.
-.SCITECO_TOPIC "!!" "EOL comment"
+.SCITECO_TOPIC "!!" comment
 The second form of real comments are end-of-line comments,
 which are analogous to C++'s \fB//\fP comments:
 .br
@@ -2322,7 +2323,7 @@ infinite one.
 Additionally \*(ST supports special colon-modified
 \(lqpass-through\(rq forms of the loop start and end commands
 for processing the argument stack dynamically.
-.SCITECO_TOPIC :>
+.SCITECO_TOPIC :> passthrough loop
 The \fB:>\fP loop end command will \fInot\fP pop values left
 on the stack since the beginning of the loop and can be used
 to aggregate stack values.
@@ -2335,7 +2336,7 @@ For instance, the following command will leave the numbers
 .EE
 The command can be understood as equivalent to the expressions
 \(lq(%a)(%a)(%a)(%a)(%a)\(rq or \(lq(%a,%a,%a,%a,%a)\(rq.
-.SCITECO_TOPIC :<
+.SCITECO_TOPIC :< passthrough loop
 Consequently, the colon-modified loop start command will
 \fInot\fP represent an argument barrier and the corresponding
 loop end command will not discard any values which is useful