removed remaining references to Github projects and updated TODO

1 files changed, 35 insertions, 8 deletions

diff --git a/TODO b/TODO
index a0fe4f0..2a18d78 100644
--- a/TODO
+++ b/TODO
@@ -7,6 +7,7 @@ Tasks:
    similar to double right click.
 
 Known Bugs:
+ * FreeBSD's `crontab -e` is not compatible with SciTECO's savepoint mechanism.
  * ncurses: GNOME Terminal and Xterm produces BUTTON3_PRESSED (without BUTTON3_RELEASED)
    events when scrolling horizontally.
    This is fixed upstream in ncurses and there is a workaround for
@@ -167,7 +168,6 @@ Known Bugs:
  * Mac OS: The colors are screwed up with the terminal.tes color scheme
    (and with --no-profile) under Mac OS terminal emulators.
    This does not happen under Linux with Darling.
-   See https://github.com/rhaberkorn/sciteco/issues/12
  * File name autocompletion should take glob patterns into account.
    The simple reason is that if a filename really contains glob characters
    and you are trying to open it with EB, you might end up not being
@@ -198,10 +198,17 @@ Known Bugs:
    also have unwanted side effects.
  * Solaris/OmniOS: There are groff build errors.
  * session.vcs does not properly work in MSYS2 environments.
- * The Windows GTK version no longer works under Wine:
+ * Wine: The Windows GTK version no longer works:
    "Failed to translate keypress (keycode: 88) for group 0 (00000409) because we could not load the layout."
    Also, all Windows builds have problems executing ECdir$ (under Wine!).
    See also https://github.com/fontforge/fontforge/issues/5031#issuecomment-1143098230
+ * Wine: --stdin is broken:
+   "g_io_channel_read_chars: assertion 'channel->is_readable' failed"
+   This among other things prevents bootstrapping and test suite runs under Wine when cross-compiling
+   from Linux or FreeBSD.
+   Therefore Windows cross compilations are currently included in .fmsbw/10-freebsd14-msys-sciteco.
+   https://bugs.winehq.org/show_bug.cgi?id=58745
+   https://gitlab.gnome.org/GNOME/glib/-/issues/3793
  * At least the GTK version with --xembed is prone to unexpected
    crashes. Interestingly, while this does leave orphaned savepoint
    files around, it does not produce a core dump.
@@ -506,7 +513,6 @@ Features:
    (and more!).
    This can be a variant of a structured error handling construct.
    This will also require managing our own function call stack.
-   See https://github.com/rhaberkorn/sciteco/issues/26#issuecomment-2449983076
  * Once we have our own function call stack,
    it will be possible, although not trivial, to add support for
    user-definable macros that accept string arguments, eg.
@@ -573,7 +579,10 @@ Features:
  * Get meta-rhaberkorn into https://layers.openembedded.org
  * AppImage via OBS.
    Apparently the AppImage repo is based on openSUSE 15.6.
-   Have to fix openSUSE 15.6 builds.
+   I have to fix openSUSE 15.6 builds.
+ * CircleCI could be used for Windows and Mac OS builds.
+   Supposedly it works from arbitrary (self-hosted) Git repositories.
+   https://circleci.com/docs/guides/plans-pricing/plan-free/
  * Bash completions.
  * FreeBSD: rctl(8) theoretically allows setting up per-process actions
    when exceeding the memory limit.
@@ -725,10 +734,6 @@ Features:
    But it would have to work with tarballs as well, so it has to be
    written into a separate header, that can be distributed.
  * Perhaps undefined operations like -(X) should check X for MININT.
- * Use Cirrus CI instead of Github Actions
-   Allows us to do CI on FreeBSD and potentially other more obscure systems.
-   Also, this will allow us to migrate to another hoster like
-   Savannah or Sourcehut later on.
  * m,nQq to get a list of codepoints from char m to n.
    This would ease subscripting, e.g. to remove the last character:
    0,:Qq-1Qq^Uq$
@@ -741,6 +746,28 @@ Features:
    as well.
  * Solaris libxcurses (/usr/include/xpg4/curses.h)
    is X/Open compatible and could be supported.
+ * Go-to labels cannot practically contain commas since when used with the <O>
+   command it would be interpreted as a label list.
+   This could be worked around by expecting label lists only if an integer
+   is given (ie. no longer imply 0).
+   However, it would be nice if we could include commas in labels of
+   the <nO> variant as well.
+   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.
+   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 be useful for =/==/===.
+ * OpenVMS port. Just for the fun of it.
+ * If nEB...$ with a non-empty string argument is disallowed for n != 0,
+   we should already throw in the process callback, to give immediate
+   feedback. Otherwise, the user might type an entire file name just
+   to find out he has to rub out everything and retype.
 
 Optimizations:
  * Use SC_DOCUMENTOPTION_STYLES_NONE in batch mode.