* Useful for packaging on platforms where we can only build from tarballs (FreeBSD)
* I don't know whether it's always safe and correct to install this file into $DATADIR/applications,
  so the file is only distributed but not installed yet.
* It contains a hardcoded binary name "gsciteco". This could actually differ
  depending on the concrete --program-prefix and it would be good to include the exact
  installation path.
  This however is not possible as long as we do not install this file.

* This is also the base of $SCITECOPATH.
* Changing it is useful for packaging where it is not possible to factor out the common
  files between Curses and Gtk builds into a "sciteco-common" package.
  As an alternative, you can now create disjunct sciteco-curses and sciteco-gtk packages.
* You will most likely want to use this for Gtk builds as in:
  --with-interface=gtk --program-prefix=g --with-scitecodatadir=/usr/local/share/gsciteco.

* The lexer.test.* macros don't work on the unnamed buffer,
  so any per-language indention settings etc. could be accidentally
  applied to the unnamed buffer.

* Since Scintilla no longer automatically scrolls the caret (see 941f48da6dde691a7800290cc729aaaacd051392),
  the caret wouldn't always end up in the view on startup.
* Added teco_interface_refresh() which includes SCI_SCROLLCARET and
  is invoked on startup. This helps with the Curses backend.
  It also reduces code redundancies.
* On Gtk, the caret cannot be easily scrolled on startup as long as no size is allocated
  to the window, so we also added a size-allocate callback to the
  window's event box. Sizes are less often allocated to the event box than to the
  window itself for some strange reason.

* This probably did not cause any bugs.

* On FreeBSD both the dlmalloc replacement and poll-thread via sysctl() work
  but the poll-thread has been benchmarked to be significantly faster,
  at least on my machine.
  You can still ./configure --enable-malloc-replacement of course.
* Interestingly, the RSS of the process visible via htop does not decrease
  after OOMs or command-line terminations - with neither of the implementations.

* it appears to behave similar to Mac OS with regard to recursions

* This especially fixes spawning on 0,128ED-mode broken since
  f557af9a9112955d3b65f6ad0d54c0791189f961.
* The process is added to a job object now, which allows us to
  kill the entire process tree.
  Previously we we were leaving around orphaned processes.