No full measurement is needed, since most of the time the longest line will
be scrolled out of view, and we're only interested in its length.

Issue #1275

Closes #1274

Closes #1268

Closes #1264

- handling special keys better for commands requiring a character
- r can operate on selection
- fixed: t moves back if character not found
- +/-/_ via extension of moveByLines motion

Issue #1268

It fails on Travis, but not on my local machine's Phantom or in a real
Webkit, so I'm going to assume it's a spurious failure.

(but only remotely).

A call to replaceRange hadn't been updated to its new signature.

The old mode was not supporting many rST constructs, or not in
sufficient detail. Features/changes:

 * no `backUp` ops to keep things fast;
 * kept `python` inner mode integration;
 * added `latex` inner mode;
 * eliminated `verbatim` configuration parameter;
 * eliminated non-standard tokens: the old mode was producing `footnote`
   and `citation` tokens, which were replaced with `quote`;
 * many more details: visually compare highlighting between old and new
   to get an impression;
 * MIT license (copied and adapted form `python` mode);

And use the editor-wide option when no value is found on the mode.

Issue #1281

+ add CodeMirror Movie link

… screen

Closes #1290

Also includes improved support of nested lists.

Closes #1276.

Add support for nesting and avoid hiding code highlighting.

Related to #1276 (but blockquotes, instead of lists).

Should use `em` or `strong` instead.

Per Dingus.

Closes #1284

Closes #1292

Closes #1291

Closes #1165.

Previously, lists following other content weren't always highlighted.

Functionality and error messages match the latest vim 7.0 release.

(->> 'clojure.core ns-publics (map first) sort (clojure.string/join " "))

Fixes Issue #1301

StringStreams.prototype.column was always calculating the column offset for a
position by walking from index 0 in the string to the current start position.
That is factorial in performance and gets noticeably slower with long lines.

StringStreams only ever advance forward. So when determining the column we can
cache the value for a previous position on the line. Then the next time column
is called, we only need to update the cache for the small portion that the
Stream advanced. This way we only ever walk the stream once.

StringString.prototype.match(<string>) may do a lot of unnecessary work:

  - If it is caseInsensitive it was calling toLowerCase on the entire string.
  - It did an indexOf search through the string for a pattern, but only cared
    if the string started with that pattern.

Because a string pattern has a fixed length, we only need to run toLowerCase
on a small substring of the stream, and we only compare this small substring
to the pattern.

This was causing "1^2" to tokenize as: (number, "1"), (variable, "^2). By
tokenizing these bitwise operators as operators CodeMirror can correctly
syntax highlight the 2 as a number. Likewise the number in "~0".

Issues #988, #742, #612, etc. show that CodeMirror users tend to:

1. Not find how to make the Tab key insert spaces instead of a tab,
2. Miss how to use extraKeys to easily solve the issue.

Adding an example helps them find a solution immediately.

Closes #1310