It will be useful for implementing LSP support.
It does not have JSON escape/unescape functions, so those
will still have to be written.

Source: https://github.com/rxi/sj.h

* It's already used on home:rhaberkorn:sciteco:UNSTABLE (OBS).
  We cannot introduce it in STABLE though until the next stable release
  which will contain the gtk-broadway-run.sh script.
* The FreeBSD packaging is actually not tested yet.
  The package version had been dumped to 2.6.0 since it definitely
  won't work with v2.5.2 tarballs.
  The v2.5.2_1 patches have consequently also been removed.
  You can still find them in the bugzilla ticket (not merged into ports yet).

This for the first time mentions all of the bundled core libraries
in the end user documentation.

* terex is based on Henry Spencer's regular expression engine for Tcl.
  It is a hybrid NFA/DFA design which has better worst-time runtimes than
  the backtracking PCRE. Memory usage is also limited and can no longer
  increase catastrophically.
* It should no longer be possible to crash SciTECO with pathological
  searches.
* Since it reliably supports partial matches (REG_EXPECT) we can
  now enable the new backwards-search algorithm by default.
  This used to be broken because of a glib bug, which I already
  fixed. It would however take a long time until this ends up
  on the majority of glib installations.
* Regexp executions can still be quite slow if you are looking
  for a pattern at the end of a huge file, which can hang the editor,
  but this can now at least theoretically be solved by adding
  hooks into terex to poll for interruptions.
* We can now also get rid of a TECO-pattern to regexp translation
  step by directly generating terex tokens (TODO).
* Performance-wise terex appears to be slower than PCRE for simple
  forward searches even when linking everything with optimzations (FIXME).
* Having a stand-alone regular expression engine is also a huge
  step in getting rid of glib.

See also: https://git.fmsbw.de/terex/about/

In principle the debian/ subdirectory is redundant with the
files in OBS. It is only still useful when building with distribute.mk
or as a template for future adoption into the Debian repositories.

Improves readability of the log files.