* There are cases, especially where the entire buffer is piped through some
  external process or when removing and reinserting large parts of the buffer,
  that dot changes very little, but the vertical scrolling position gets resets.
  This is especially noticable with the macro @^U{[: HECcat$ ]:},
  but also with M#cf (clang-format wrapper from "Useful macros").
* We now try to preserve the vertical position ("first visible line")
  before scrolling caret.

This is hardcoded, but in line with the current defaults from
fnkeys.tes.

* Both the WinGUI and Wincon variants have their own idiosyncrasies:
  * WinGUI ignores `mouseinterval(0)` and may report BUTTONX_CLICKED
    for very quick clicks.
    Therefore we now emulate separate PRESSED/RELEASED events.
  * Wincon does not report BUTTONX_RELEASED at all.
    Therefore we still enable click detection, so that fnkeys.tes will
    work at least partially.
    Therefore we also enable REPORT_MOUSE_POSITION, so that
    right-click-dragging will work.
    This should still be fixed in PDCurses upstream, though.
* See also https://github.com/Bill-Gray/PDCursesMod/issues/330

* The old heuristics - scroll if dot changes after key press -
  turned out to be too simplistic.
  They broke the clang-format macro (M#cf), which left the view at the
  top of the document since the entire document is temporarily erased.
  Other simplified examples of this bug would be:
  @^Um{[: HECcat$ ]:} Mm
  Or even: @^Um{[: H@X.aG.a ]:} Mm
* Actually, the heuristics could be tricked even without deleting any
  significant amount of text from the buffer.
  The following test case replaces the previous character with a linefeed
  in a single key press:
  @^Um{-DI^J$} Mm
  If executed on the last visible line, dot wouldn't be scrolled into the view
  since it did not change.
* At the same time, we'd like to keep the existing mouse scroll behavior from
  fnkeys.tes, which is allowed to scroll dot outside of the visible area.
  Therefore, dot is scrolled into view always, except after mouse events.
  You may have to call SCI_SCROLLCARET manually in the ^KMOUSE macro,
  which is arguably not always straight forward.
* Some macros like M#cf may still leave the vertical scrolling position
  in unexpected positions. This could either be fixed by eradicating all
  remaining automatic scrolling from Scintilla or by explicitly restoring
  the vertical position from the macro (FIXME).
* This was broken since the introduction of mouse support,
  so it wasn't in v2.3.0.

* Unfortunately we cannot use `wbkgdset(win, A_REVERSE)` if we plan to
  use reverse text on this background, i.e. if we want to cancel out the background A_REVERSE.
* SciTECO therefore no longer uses background attributes, but only foreground attributes.
  When setting a reverse text, we XOR A_REVERSE into the previous attributes.
* This fixes control characters especially in the info line and popups, as well as rendering
  of the popup scroll bars.
* The command-line should now be rendered properly even on a dark-on-bright color theme
  (which does not yet exist).

This requires Unicode icon support to be enabled via ED.
The ellipsis symbol is shorter and more distinctive, allowing more of the original
text to be preserved before truncation.

* SCI_COLOR_PAIR() is now a function teco_color_pair() since it also became
  an inline function in Scinterm.

* Highlights both 1st level and 2nd level quotes and signatures.
* This also sets the edge to 78 columns, as is recommended for email and
  enables word wrapping.
  The edge mode is not set, since it kind of looks ugly in Scinterm.
* Helps when using SciTECO as the email editor for instance in the
  Aerc mail client.
* Unfortunately, we cannot set up Scintilla to automatically break words
  after 78 columns (or perhaps that's a good thing).
  You can use the M#rf reformat-paragraph macro to reflow paragraphs
  before sending the mail.
  This will take the edge column into account even if no edge mode is set.

* If the background color would be non-black, render text in reverse
  video. ncurses doesn't do that automatically.
* Fixes rendering under historical terminals like VT100 and VT240,
  but also all of the monochrome versions of modern emulators in terminfo.
* This also improves the situation when $TERM is set to something conservative,
  e.g. when connecting via RS232.
* Scinterm is temporarily changed to my own fork, which already contains
  a monochrome patch.