* Turns out that it works perfectly with the default --enable-malloc-replacement
  as malloc() is replaced globally.
* Added note to configure.ac that malloc() replacement may be useful on platforms
  without a global symbol namespace - you just have to link statically (--enable-static-executables)
  as well.
  This wasn't necessary on Haiku, though.
* Only the test suite required a minor fix since Haiku doesn't support `ulimit`.
* The Gtk interface is broken though on Haiku: You cannot type dead keys,
  Ctrl and AltGr combinations.
  Doesn't appear to be SciTECO-specific though. The libraries simply doesn't
  report modifiers. Appears to be a bug in Haiku's GTK 3 port,
  at least in their Beta5 branch. It can be reproduced with gtk-demo as well.
* This opens the door for contributing a port into HaikuPorts.
  This will probably be Curses-only for the time being (see above).

* This can be used for bootstrapping Windows binaries cross-compiled on FreeBSD or Linux
  without requiring a native build to be installed first.
  It will also allow running the test suite under Wine.
  While Linux allows registering Wine as the launcher via binfmt_misc,
  on FreeBSD we have no choice than to use --with-launcher.
* Unfortunately, SciTECO cannot currently be properly built with versions running under Wine
  and the test suite also fails.

* DEC TECO had an <EO> command.
  In contrast to DEC TECO's implementation, the value reported by
  <EO> encodes a major.minor.micro semantic version.

* Test cases where hard to read since there was a layer of shell and M4 escaping -- sometimes
  with the help of quadrigraphs -- to preserve the original TECO characters.
* We introduced TE_CHECK() and TE_CHECK_CMDLINE() M4 macros which care about shell escaping
  automatically.
* If all TECO code is double quoted with [[ and ]], single square and round brackets
  are preserved as well.
* Only in case of using *unbalanced* single square brackets, you have to take action
  and add `![!` or `!]!` TECO comments to balance them out.
  This is still better than quadrigraphs.
* The $ESCAPE and $RUBOUT environment variables are replaced by equivalent
  M4 macros, so they can be used with TE_CHECK_CMDLINE().
* Other references to shell variables have been resolved by exporting them
  into the environment (as in the case of $srcdir) or by introducing
  new M4 macros (TE_MAXINTxx, TE_MININTxx).
* The $WORDS_EXAMPLE variable has been got rid of by writing it into a temporary
  file instead. There is some redundancy -- in principle an M4 macro could have also been used.
* This leaves only 6 remaining usages of AT_CHECK() for invoking SciTECO,
  mainly for testing opener.tes, where we have to pass in command line arguments.
  In theory most of them could be avoided as well by preparing the unnamed buffer appropriately.
  However the way that command line parameters are passed will be changed sooner or later.
* This uses GNU M4 extensions, but Autoconf requires that anyway.

* After detecting +line[,column] constructs, the next argument is not parsed as a potential
  filename:line[:column] construct.
* This code turned out to be tricky to get right, so I added a test case.
  Standard library modules can well be checked in the test suite since
  we have $SCITECOPATH pointing to the source tree's lib/ directory.
* Make sure that relevant variables from atlocal.in are really exported into the
  process environment.
  This was also broken for the Glib debug options.

* In other words, fixed `-9223372036854775808\` on --with-teco-integer=64
  (which is the default).
* The reason is that ABS(G_MININT64) == G_MININT64 since -G_MININT64 == G_MININT64.
  It is therefore important not to call ABS() on arbitrary teco_int_t's.

* This was actually broken if the command is preceded by `@` and `:` characters, which
  are __not__ modifiers.
  E.g. `Q:@I/foo^W` would have rubbed out the `:` register as well.
* Also, since it was all done in teco_state_process_edit_cmd(),
  it would also rub out modifier characters from within string arguments,
  E.g. `@I/::^EQ^W`
* Real commands now have their own ^W rubout implementation, while the generic
  fallback just rubs out until the start state is re-established.
  This fails to rub out modifiers as in `@I/^W`, though.
* Real command characters now use the common TECO_DEFINE_STATE_COMMAND().
* Added test cases for CTRL+W rub out.
  A few control characters are now portably available to tests
  via environment variables `$ESCAPE`, `$RUBOUT` and `$RUBOUT_WORD`.

This became the default in later Valgrind versions.
With leak checking, the test suite does not currently run cleanly.

* <W> was also using keyboard movement commands.
* This fixes an inconsistency between the handling of punctuation characters,
  e.g. "(word" followed by -W vs. Y.

* The program exit code will usually not signal failures since they are caught earlier.
* Therefore, we always have to capture and check stderr.