Christian Clason

It does: ```vim setlocal commentstring=\ \ \ \ \ \ *%s ```

And also COBOL?

`:Explore` is _not_ an "essential Vim built-in command"; it's a command provided by the (bundled) plugin netrw (which we plan to remove and replace with a more suitable, modern, alternative...

We do not maintain these files; please contact the maintainer listed at the top of the file and propose the change; if there is no response, you may raise an...

Yes (and to make sure that any improvements benefit both projects). This is an ironclad project policy.

While we're blue-skying: https://zed.dev/blog/zed-decoded-tasks (In general, it's hard to draw the line here between what should be in core and/or default and what should be a plugin.)

I don't think we need to expose that as public API. The name and docstring is also misleading; there's nothing "resolved" here, as the buffer number -- if passed --...

I disagree; most of these cases should be handled by consistent convention (`bufnr` is mandatory with `0` for current). We should _never_ use `nil` for current in our codebase.

I agree that my "terminal colors should match parent shell" objection does not apply here, I am still hesitant to use the Neovim colors for terminal colors, for the following...

https://ecma-international.org/wp-content/uploads/ECMA-48_5th_edition_june_1991.pdf (page 61-62)