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.

1 files changed, 1 insertions, 5 deletions

diff --git a/TODO b/TODO
index c1088b5..514ad4f 100644
--- a/TODO
+++ b/TODO
@@ -1018,11 +1018,7 @@ Optimizations:
 Documentation:
  * Doxygen docs could be deployed on Github pages
    automatically.
- * The ? command could be extended to support looking
-   up help terms at dot in the current document (e.g. if called as .?$
-   similar to .FT$).
-   `?$` could also toggle through all results just like `FT$`.
-   Furthermore, womanpages could contain "hypertext" links
+ * Womanpages could contain "hypertext" links
    to help topics using special Troff markup and grosciteco support.
  * The command reference should include an overview.
  * Command reference is poorly formatted.