Issue #5016

Issue #5016

Issue #5013

To avoid bad parses when unary and binary operators are squashed
together without spaces.

Issue #5013

This is to prevent the closure compiler from failing with

bazel-out/darwin_x86_64-fastbuild/bin/polygerrit-ui/app/gr-app.js:51233: ERROR - Bad type annotation. expected closing } See https://github.com/google/closure-compiler/wiki/Bad-Type-Annotation for more information.
     * @return {Object{from:number, to:number, line: number}} The boundaries of
                      ^
  ProTip: "JSC_TYPE_PARSE_ERROR" or "checkTypes" can be added to the `suppress` attribute of:
  //polygerrit-ui/app:polygerrit_ui_closure_lib
  Alternatively /** @suppress {checkTypes} */ can be added to the source file.

1 error(s), 1 warning(s)

Closes #5009

Since it produces orderings that don't correspond to what
the browser does then.

To take document direction into account

Happened if you entered visual block mode in one editor and then tried to exit insert mode in another, since lastChange comes from vimGlobalState.

Closes #4999

When submitting the previous commit, I had not noticed that the parameter allowAtxHeaderWithoutSpace had type Object instead of type boolean. I've fixed this now.

Adding documentation for the `allowAtxHeaderWithoutSpace` configuration parameter.

Issue #4987

Closes #4986

Closes #4878.

Closes #4954

Though the decorator proposal doesn't support this, it is
apparently something TypeScript adds.

Closes #4959

Issue #4926

Issue #4981

Improved the description of "make the problem occur", explaining that maintainers want to reproduce the error.

Mentioned CodeMirror's great ability to highlight code.

@param specified in a template comment is older but still supported way of
declaring a parameter. The comment must directly precede {template}.

Reference: https://developers.google.com/closure/templates/docs/concepts#namespace-decl