updated TODOHEADmaster-fmsbw-cimaster

1 files changed, 5 insertions, 9 deletions

diff --git a/TODO b/TODO
index 605be9d..9318dc6 100644
--- a/TODO
+++ b/TODO
@@ -1,13 +1,10 @@
 Tasks:
  * Have a look at TECO-86.
  * VEDIT and PMATE for MS-DOS
- * Make sure that fmsbw.de is indexed by Google
  * Update all CI pipelines to freebsd/freebsd-runtime:15.1
    This also means we'll have to update the server first.
  * Build FreeBSD GTK versions and run test suite as part of CI.
    Try to run against broadwayd instead of Xvfb.
- * Add SciTECO to the official list of LSP implementations:
-   https://microsoft.github.io/language-server-protocol/implementors/tools/
 
 Known Bugs:
  * GTK on Windows 11: Doesn't do anti-aliasing on all screens.
@@ -573,11 +570,12 @@ Features:
    https://github.com/fpjohnston/TECO-64/blob/master/doc/oper.md
    However, instead of introducing a separate parser state, better
    use operators like ~=, ~< etc.
-   * Alternatively, `~` might be a good choice as a shorter alternative
-     to XOR, allowing for the idiom `Qa~Qb"=` when checking for equality
-     that is faster than using `-` and works for floats as well.
  * ^& could be a NAND operator.
+ * ^% as a synonym to ^/
  * ^< left shift, ^> right shift
+ * Perhaps all operations on integers should be checked for overflows
+   using the appropriate GCC intrinsics.
+   There is probably little benefit in having unchecked operations.
  * It should be possible to disable auto-completions of one-character
    register names, so that we can map the idention macro to M<TAB>.
  * Add a configure-switch for LTO (--enable-lto).
@@ -748,15 +746,13 @@ Features:
    Also, labels cannot contain `!`.
    The "," and "!" restrictions are mainly relevant when using computed
    gotos in O^EQ[label]$ as you cannot match arbitrary strings.
- * pad,n\ to format number with padding.
+ * pad,n\ and pad,n= to format number with padding.
    Allowing `\` to format multiple numbers when called with a list
    of numbers makes little sense.
    I find myself wanting to pad numbers, especially hexadecimal numbers,
    often. If <pad> is negative it might perform a right padding with
    spaces.
    To format a hex byte, you would write 16^R 2,Qa\ ^D.
-   The same extension might not be desirable for =/==/===, unless
-   they are colon-modified?.
  * Scinterm: INDIC_PLAIN and INDIC_STRIKE could theoretically be supported.
    PDCurses has A_STRIKETHROUGH. This would require Scintilla API
    changes, though, as it currently calls SurfaceImpl::FillRectangle(),