* hash-bang lines in grosciteco.tes and tedoc.tes are fixed up
  at build time instead of install-time (via install-exec-hook).
* This will hopefully resolve problems with the FreeBSD port,
  since Poudriere installs the package as non-root but with BINMODE=555.
  The alternative would have been to set BINMODE=755 in the port which may not
  be acceptible by the official port committer.
  Anyway, I decided to go out of the way of any conflicts.
  See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?format=multiple&id=283601
* On the downside, this will break install-path overrides at install-time
  (e.g. `make install bindir=...`).

* They have a newer version in pkgsrc, but it's not even available
  as a binary package on the arm6.
* Has some glitches, e.g. does accept the ASCII 27 in tutorial.ms,
  but it's probably not worth to work around.

* The unnamed buffer is also used for reading from --stdin, so you couldn't practically combine
  --stdin with passing command-line arguments to macros.
* The old approach of passing command-line arguments via lines in the
  unnamed buffer was flawed anyway as it wouldn't work with filenames containing LF.
  This is just a very ancient feature, written when there weren't even long Q-reg names in SciTECO.
* You can now e.g. pipe into SciTECO and edit what was read interactively, e.g. `dmesg | sciteco -i`.
  You can practically use SciTECO as a pager.
* htbl.tes is now a command-line filter (uses -qio).
* grosciteco.tes reads Troff intermediate code from stdin, so we no longer need
  "*.intermediate" temporary files.
* added a getopt.tes test case to the testsuite.
* This change unfortunately breaks most macros accepting command-line arguments,
  even if they used getopt.tes.
  It also requires updating ~/.teco_ini - see fallback.teco_ini.

* We have to avoid `/*` within comments, so one of the two characters will
  have to use a named glyph.
  \[**] is actually a special symbol, which wasn't noticed until supporting Unicode.
  There is no named glyph for the plain asterisk.
  Thus we now use \[sl] to escape the `/` character.
  `/\c*` might have also worked.
* grosciteco now supports the `sl` glyph.

* Improves DEC TECO-11 compatibility.
* <EM> is still supported as a synonym, but considered deprecated and is no longer documented.
  A warning is printed when invoked.
  It can be repurposed at any time in the future.
* `EI$` is not yet supported.
  I am unsure whether this makes any sense.

* Support fold level configuration using `.SCITECO_FOLDLEVEL`.
  This sets the current output line as the fold header and all subsequent lines
  with the given fold level (until another `.SCITECO_FOLDLEVEL` instruction
  is encountered).
* This is now done automatically for man's SH and SS macros,
  so the man-page based woman pages provide folding.
* The folding margin is therefore now always enabled in fallback.teco_ini.

* In the grosciteco-generated .woman.tec files, the fonts were only
  set on the monospaced styles if lexer.font was set since it was
  undefined by default.
  We'd need a lare IF-ELSE statement to handle that in womanpages
  since woman.tes changes the default font to a variable-width font.
  Just leaving the default font, therefore won't work.
* We now always initialize lexer.font in lexer.tes.
  You no longer have to check for its existance.
* Consequently, you can no longer set lexer.font *before* munging
  lexer.tes because it will be overwritten.
  At least not without additional checks.
  Such a design is not suggested by fallback.teco_ini, though.
* Fixes monospaced sections in the tutorial and other womanpages on Gtk.

* grosciteco was just hardcoding "Monospace", regardless of what was configured via lexer.font in ~/.teco_ini
* The variable-width font used for ordinary "womanpage" body texts was hardcoded to "Serif".
  It is now configurable via the lexer.woman.font register.
* There is a difference, though:
  lexer.font has no default value and must therefore be checked everywhere.
  This is so you can set it even before munging lexer.tes.
  lexer.woman.font however has a default (Serif), so it can only be overridden after
  munging lexer.tes.
  Perhaps it would be easier and more consistent to have a default for lexer.font as well.

This fixes building of the new tutorial.woman on Ubuntu.

* They swap the default order of skipping characters.
  For positive arguments: first non-word chars, then word chars.
* This is especially useful after executing the non-at-modified versions.
  For instance, at the beginning of a word, `@W` jumps to its end.
  `@V` would delete the remainder of the word.
* Since they have to evaluate the at-modifier, which has syntactic
  significance, the command implementations can no longer use
  transition tables, so they are in the switch-statements instead.