Selecting two full lines including line ends makes a selection from
line 1 to line 3 (ch: 0). This command used to sort three lines (1 to
3) which is not what I expect. This change makes it sort only two
lines if there are no selected characters on the last line.

It also fixes a fatal error if there are more than one selection on
the same line (the code used 'range' instead of 'ranges').

It also selects the trailing newline after sorting the lines so that
the whole lines are selected.

Closes #3909

Add template/variable definitions, checking, types, additional
keywords and indentation fixes.

 - Added for as a defining keyword
 - Added new types and operators
 - Fixed numbers so basic integers are represented
 - Identifiers can now be surrounded with backticks
 - Properties and #/@ instructions are now distinct, with the latter represented as a builtin type
 - Properties are now matched before punctuation. Code can now fold.
 - Remove the regexp checking as that syntax does not currently exist in Swift
 - Added tests

With non-empty selections, transposeChar would only work on the chars next to
head and ignore the selected chars. Also, a cursor at line start was not moved
on successful swapping.

And don't block-comment inside a block comment

Closes #4208

And hopefully get Travis to run our tests again

Issue #4188

Closes #4148

In Replace mode (or Overwrite mode) it should still go backwards
without deleting characters.

Issue #4038

@ as __matmul__ operator only on Python 3,

Add tests for Python mode for this use case.

Closes #3957

There were two issues:

1. Github flavored markdown calls Objective C `objective-c`
2. The gfm.js mode didn't include `-` in its fenced code block regex

Additionally, test/index.html did not import the mode/meta.js file,
which prevented mode lookup by name from working in unit tests.

Added tests and fixed some issues uncovered by testing.

 * Support nested block comments.
 * Improve number and operator parsing.
 * Improve string parsing.
 * Style brackets correctly.
 * Improve #-words.

Closes #3840

Closes #3742
Closes #3744

zt was placing 40% of the line above the visible area, and zb was placing it too high.

Which is kind of arbitrary but seems to give less surprising
results.

Issue #3658

The code is now clearer, and will prefer the nearer end of the atomic
range as long as that means there is still progress (i.e. the cursor
does not get stuck).

Issue #3658