1. End of wrapped line in bidi content is wrong (my mistake)
2. coordsChar({left:0, top: *}) in bidi content is wrong after Marijn's code
   style changes

ES5, breaking up of whitespace tokens

* Enable most in phantom
* Enable all in !phantom
* Disable two that trigger L1 which we don't do correctly currently
* Revert commit 5cc5d7f50efc7a016485f017a603c4fa2b035266 (L1 tests)

Should fix #1862 for ltr text.

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.