We don't use the return value of getNestingLevel(), only its
nestingLevelsPop() semantics. Get rid of the return value and rename the
function to avoid confusion.

They are already fixed upstream, so it doesn't add to the diff.

Signed-off-by: Masatake YAMATO <yamato@redhat.com>

main/field.c:968:23: warning: \
     suggest braces around empty body in an ‘else’ statement [-Wempty-body]

     AssertNotReached();
Signed-off-by: Masatake YAMATO <yamato@redhat.com>

# Conflicts:
#	ctags/main/lcpp.c
#	ctags/main/parse.c

The previous code would skip parsing with sub-parsers so these would not
work. Running full createTagsWithFallback1() in this case would cause
two problems:

1. We would have to propagate the extra callback arguments to
runParserInNarrowedInputStream()

2. And the callbacks after each pass should not actually be called in this
case because the caller expects these are called for the master parser,
not the sub-parsers.

So instead just do simple parsing without re-tries which are used only in
the C and Fortran parsers which lack sub-parser capability anyway.

Update link to GTK+3 bundle for test builds to self-hosted version

Update Scintilla to version 3.10.0

Fixes #1421.

The host win32builder.gnome.org seems dead and so host the GTK+3 bundle
we use to test builds for Windows cross-compilation on our own.

Pango now requires fribidi, so we need to install it.
Update the download URL for UnxUtils.
Remove unnecessary cmake files after installation.

Update Python identifiers with Python 3.7

Now the keybinding can be overridden (e.g. using Tab for it as well as
normal behavior), beeping when there is no next cursor is more annoying
than useful.

Part of #1554.

The new styles are for "diff of a diff", e.g. lines starting with `++`,
`+-`, `-+` and `--`.  Those are currently mapped conservatively keeping
the previous display behavior, until we have good style matches for
them.

Scintilla 3.7.6/4.0.0 deprecated `SCE_*STYLEBITS*` and moved it to
deprecated features that require a build-time flag to be available.

Thus, drop use of those (as they are now no-ops anyway) and bump the
ABI (so plugins depending on those don't build mistakenly load) and API
(so a developer can guard use of those if wanted) version accordingly.

These two strings have probably been translated with a generic online tool which lacks of contextual translation

Fixes #395.

Fixes https://github.com/geany/geany/issues/1351

See also b10b2a71 (PR #1840)

Closes #1868

Fix horizontal and page scroll on GTK3

In addition, the signal allows plugins swallow the event so it's not
processed by Geany.

Small typo (grammar)

Before, **boldface** or *italics* (also _italics_) would not generally show as that, definitely not with the default color scheme. After this change, they appear with the same color as normal text but with that typography, in all color schemes.

Use HTTPS URL for domain www.geany.org

Our custom scroll handler for horizontal (Shift+Scroll) and page
(Alt+Scroll) scroll didn't properly check the scroll direction and
assume that if it's not down it's up.  This was mostly not a problem
because the other types only were left and right scroll events, which
are a lot less common.

However, it became a lot more problematic with GTK 3.4 that introduced
"smooth scrolling", and thus a new scroll type that can happen for
events in any direction.  We then would scroll up (as we assume "not
down" is up) regardless of the actual direction of the event.

It's still not clear why we'd get smooth scroll events on X11 as no
code I can find asks for it and we generally don't get those, but
sometimes a Scintilla widget starts receiving them, leading to the bug.
On Wayland on the other hand, Scintilla asks for smooth scroll events,
so we need to have a fix for it in any case.