Currently, if you perform the uncomment command with the cursor outside a single-line block comment, it will uncomment that block comment. This is unfortunate behavior for cases where the block comment is used to describe the parameter to a function like "foo(/* index */ 0)". It's also inconsistent: if you have a selection and a single-line block comment after the end of the selection, uncomment() will do nothing, however if you have a selection with a single-line block comment *before* the selection, it will line-comment out all the lines of the selection instead.

This also isn't a complete fix, but significantly reduces the scope of the problem. For example if you have "/* foo */ bar /* baz */", uncomment() still does the wrong thing when the cursor is on foo or baz.

http://lists.w3.org/Archives/Public/www-style/2014Jun/0312.html

Lost negation operator when converting to new IE flags in bbefd22a.

Issue #2635

Issue #2644

Issue #2638

Closes #2629

Closes #2623

Issue #2621

Using the CodeMirror-guttermarker and CodeMirror-guttermarker-subtle CSS
classes to give the markers their color.

Issue #2602

When using the measure div to measure a LineWidget with coverGutter: true,
set the parent's width to include the gutter. Otherwise, the widget will
be measured as if it were not meant to cover the gutter (it will be
measured at a narrower width).

Fixes #2611

Modified the lineWidgetChanged test to also test for #2611

This makes it work correctly when the hanging indent is different from the indent unit.

As described in the comment, there was actually an intermediate selection being created, which clobbered the middle-click paste buffer and thus resulted in a $ being pasted instead of the actual content the user wanted. It's still a mystery why you couldn't repro it, but my guess is that due to some configuration (maybe in your window manager) your system wasn't updating the paste buffer as eagerly as Debian and Unity do by default.

Remove off-by-one in vim when head is further forward in the document than the anchor, where vim's selection becomes 1 less than CodeMirror's. This was originally done because the cursor showed past the anchor and looked like an additional character selection.

It's intended to match a literal `{`, but that must be escaped as it's
a meta character in JS regex.

Issue #2624

Issue #2622