* This is a gimmick pseudo-game for driving a tank around your buffer.
* The tank is "animated" and crushes non-space characters it drives over.
* When shooting, it deletes characters that get hit.
* When escaping, the tank explodes and leaves a "crater" behind.

* strings are bold (if supported) and bright white
* comments are in italics (if supported by the terminal)
* otherwise this uses the same colors as terminal.tes
* should be well suited for monochrome terminals as well

tecat.tes and repl.tes are now executable scripts, even though they are
installed into the $SCITECOPATH.

This is still much slower than the Lua version here:
https://gist.github.com/rhaberkorn/6534ecf1b05de6216d0a9c33f31ab5f8

* Unfortunately, this will currently just terminate when some command fails.
  We require an error catching mechanism to fix this up.

Especially useful since Gtk users are supposed to edit ~/.teco_css.

* Unfortunately, the Lexilla lexer does not recognize PostgreSQL multiline
  strings between $$...$$.
* All of the other SQL variants, that Scite supports, are skipped for the time
  being. They'd probably have to be separate SciTECO lexer configs anyway.

The email, git and sciteco lexer configurations are bundled even
without the LEXILLA option.

* After installation, SciTECO will therefore start into a more userfriendly mode
  even if the user does not create a custom ~/.teco_ini.
  It is hoped that this will scare away less of new users, who
  are not willing to read through all of the documentation.
  Still, users are warned in the absence of ~/.teco_ini.
  This warning however, might not be immediately visible, especially
  not when running gsciteco without an attached console.
  (This will change once I redo the UI and allow a number of messages
  to be queued in the message area.)
* Theoretically, you could also just extend fallback.teco_ini from ~/.teco_ini,
  but that would require installing it into $SCITECOPATH.
* Since the fallback profile will now be munged automatically
  on a wide range of systems, we set up xclip only when detecting X11
  ($DISPLAY is non-empty).
  E.g. when running under Wayland or the Linux console, you still won't
  get the clipboard registers, which is probably better than having the
  clipboard operations fail once you try to use them.
* xclip is now "suggested" on Debian/Ubuntu.
  Unfortunately we cannot pull it in only in the presence of X11.

* This is done via the new opener.tes in the standard library.
* Some programs that use $EDITOR expect the +line syntax to work.
* You can copy filename:line:column directly from GCC error messages
  and filename:line from grep output.
* Since there may be safe file names beginning with "+" or containing colons,
  there needs to be a way to turn this off, especially for scripts that don't
  know anything about the filenames to open.
  This is done with "--".
  Unfortunately, the first "--", that stops parameter processing,
  is always removed from the command line and not passed down into TECO land.
  This is not a problem for stand-alone scripts,
  since the script filename is already stopping option processing, so "--"
  would get passed down.
  But when calling the profile via `sciteco -- ...`, you could prevent leading
  minus signs to cause problems but since the `--` is removed, opener.tes cannot
  use it as a hint.
  Therefore, we introduced `-S` as a new alternative to `--`, that's always passed
  down as `--` (i.e. it is equivalent to "-- --").
  In other words, `sciteco -S *` will always open exactly the specified files
  without any danger of misinterpreting certain file names.
  Should we ever switch to a custom option parsing algorithm, we might preserve
  "--" (unless after --mung) and thus get rid of "-S".
* This advanced behavior can be tweaked by the user relatively easily.
  In the easiest case, we could replace M[opener] with
  <:L;R 0X.f [* @EB/^EN.f/ ]* L>
  in ~/.teco_ini to completely disable the special syntax.