~gpanders/gpanders.com

3951c39ee99377c078fd2f5e51dcb4f8d4c8e672 — Gregory Anders a month ago 58700f6
Update "What's New in Neovim 0.10"
M content/blog/whats-new-in-neovim-0.10.md => content/blog/whats-new-in-neovim-0.10.md +277 -27
@@ 1,6 1,6 @@
---
title: "Whats New in Neovim 0.10"
date: 2024-03-15T07:06:36-05:00
title: "What's New in Neovim 0.10"
date: 2024-05-07
tags: [neovim]
draft: true
---


@@ 24,68 24,318 @@ are some of the highlights.

## Table of Contents

* [New default colorscheme](#new-default-colorscheme)
* [Defaults](#defaults)
* [Builtin commenting](#builtin-commenting)
* [Terminal UI enhancements](#terminal-enhancements)
* [LSP inlay hints](#lsp-inlay-hints)
* [Tree-sitter query editor](#tree-sitter-query-editor)
* [New 'winfixbuf' option](#new-winfixbuf-option)
* [Miscellaneous](#miscellaneous)
* [Roadmap](#roadmap)

## New default colorscheme
## Defaults

Original issue: https://github.com/neovim/neovim/issues/14790
PR: https://github.com/neovim/neovim/pull/26334
### Colorscheme

Credit: Evgeni Chasnovski ([@echasnovski][])
Nvim has been in need of a new default colorscheme for a long time. While the
default colors indeed have some charm and nostalgia, there are serious
accessbility and aesthetic issues, particular when using Nvim is a diff
viewer. The screenshot below shows the default colorscheme before Nvim 0.10:

{{< figure src="/img/nvim-colorscheme-old.png"
           alt="Neovim's default colorscheme before 0.10" >}}

Nvim 0.10 now ships with a new default colorscheme, which you can see below:

{{< figure src="/img/nvim-colorscheme-new.png"
           alt="Neovim's new default colorscheme" >}}

The new default colorscheme was heroically contributed by [Evgeni
Chasnovski][@echasnovski], who endured endless bikeshedding and successfully
navigated the treacherous waters of Opinion. There were many constraints
imposed on the design of the colorscheme, which you can read in the
[PR][#26334] (and the many follow up PRs and issues linked therein). It is
quite literally impossible to please _everyone_ with a single colorscheme, and
there is no expectation that we have achieved that, but the new colorscheme
does, hopefully, improve the default experience for many people.

[@echasnovski]: https://github.com/echasnovski
[#26334]: https://github.com/neovim/neovim/pull/26334

### LSP and Diagnostics Mappings

Nvim 0.10 adds [default mappings][#28500] and options for some common LSP
functions (these are in addition to the existing defaults mentioned in `:h
lsp-defaults`):

* `K` in Normal mode maps to `vim.lsp.buf.hover()` unless `'keywordprg'` is
  already set to a non-default value. Use this to view information about the
  function or variable under the cursor.
* `crn` in Normal mode maps to `vim.lsp.buf.rename()`. Use this to rename the
  identifier under the cursor.
* `crr` in Normal mode and `<C-R>r` (or `<C-R><C-R>`) in Visual mode maps to
  `vim.lsp.buf.code_action()`.
* `gr` in Normal mode maps to `vim.lsp.buf.references()`. Use this to find
  references to the identifier under the cursor.
* `<C-S>` in Insert mode maps to `vim.lsp.buf.signature_help()`. Use this to
  display the signature of a function in a floating window.

In addition, there are new [default mappings][#16230] for navigating diagnostics:

* `[d` and `]d` in Normal mode map to `vim.diagnostic.goto_prev()` and
  `vim.diagnostic.goto_next()`, respectively. Use these to navigate between
  diagnostics in the current buffer.
* `<C-W>d` (and `<C-W><C-D>`) in Normal mode map to
  `vim.diagnostic.open_float()`. Use this to view information about any
  diagnostics under the cursor in a floating window.

The `cr` prefix has the mnemonic of "**c**ode **r**efactor". This slots in
nicely alongside Tim Pope's [vim-abolish][] plugin which also provides some
`cr` prefixed mappings to change the "case" style of identifiers (e.g.
`snake_case` to `PascalCase`).

`gr` and the diagnostics mappings override builtin mappings. These builtin
mappings are not often used, but if you _do_ use them you can delete the new
default mappings with `vim.keymap.del()` or `:unmap`.

The intention behind providing more default mappings is to make it easier to
get started with LSP in Neovim. You may also notice that the instructions in
the [nvim-lspconfig][] repo have been substantially pared down and reduced.
The hope is that most users should be able to get up and running with useful
LSP features with little to no configuration and without needing to write a
bunch of Lua code.

Two features which many users rely on for their LSP experience are snippets
support and completion. Both of these features are on the roadmap to be
included in Nvim core (related: [#27339][], [#25696][], [#25670][]) which
will, hopefully, make the experience of using LSP in Neovim even smoother in
the future.

[vim-abolish]: https://github.com/tpope/vim-abolish
[#28500]: https://github.com/neovim/neovim/pull/28500
[#16230]: https://github.com/neovim/neovim/pull/16230
[nvim-lspconfig]: https://github.com/neovim/nvim-lspconfig
[#27339]: https://github.com/neovim/neovim/pull/27339
[#25696]: https://github.com/neovim/neovim/issues/25696
[#25670]: https://github.com/neovim/neovim/issues/25670

## Builtin Commenting

Longtime Vim users are likely familiar with the venerable [vim-commentary][]
plugin, which creates mappings and operators for commenting and uncommenting
text. Thanks to [Evgeni Chasnovski][@echasnovski], Nvim 0.10 now [bundles this
functionality][#28176] by default, using a from-scratch implementation in
Lua. Unlike vim-commentary, Nvim's builtin implementation provides a text
object and supports Tree-sitter, which is useful when working in injected
languages (example: if you comment text inside a `<script>` tag in an HTML
buffer, it will correctly use the Javascript `//` comment string rather than
HTML's `<!-- -->` comment string).

See `:h commenting` for more details.

[vim-commentary]: https://github.com/tpope/vim-commentary
[mini.comment]: https://github.com/echasnovski/mini.comment
[#28176]: https://github.com/neovim/neovim/pull/28176

## Terminal UI enhancements

- 'termsync'
- OSC 52
    - Automatic support with XTGETTCAP
- OSC 8
- Auto-enable truecolors when supported
    - DECRQSS
    - XTGETTCAP
Nvim 0.10 adds support for many new terminal based capabilities.

### Synchronized Output

Many modern terminal emulators support [synchronized output][] which allows
terminal applications (like Nvim) to "batch" all of their UI updates in the
terminal emulator and display them all at once. This can reduce "flickering"
and "tearing" when a terminal UI (TUI) is being drawn very rapidly. This can
sometimes happen in Nvim when using plugins that perform rapid UI updates
(e.g. spinners, LSP status windows, etc.). Nvim 0.10 introduces a new
`'termsync'` option (enabled by default) which enables this feature if it is
supported by the terminal emulator.

[synchronized output]: https://gist.github.com/christianparpart/d8a62cc1ab659194337d73e399004036

### System clipboard synchronization

Nvim 0.10 can now use the OSC 52 escape sequence to write to (or read from)
the system clipboard. OSC 52 is only used automatically when (1) it is able to
determine that the terminal emulator supports it (via XTGETTCAP), (2) it is
running in an SSH session, and (3) when the `'clipboard'` option is unset.
Note that some terminal emulators do not support reading from the system
clipboard with OSC 52, or only allow it after prompting the user for
confirmation. It is recommended to use the traditional "paste" key binding
(e.g. `Cmd+V` on macOS or `Ctrl+Shift+V` on Linux) to paste into Nvim from the
system clipboard and use `"+` to copy to the clipboard inside Nvim (see `:h
quoteplus`).

### Hyperlinks

Nvim 0.10 introduces experimental support for hyperlinks using the OSC 8
sequence. By default, this is used in Markdown for links of the form
`[example](https://example.com)`. If your terminal emulator supports the OSC 8
escape sequence, then the text `example` in the Nvim buffer will contain a
hyperlink that can be clicked and will open `https://example.com` in your web
browser.

This means that users can view Markdown files with `:set conceallevel=2` and
get an experience much closer to the rendered output:

{{< figure src="/img/nvim-readme.png"
           alt="Screenshot of the Neovim README opened in Nvim" >}}

Note that the underlined words in the screenshot are clickable link text, just
as you would find in a web browser.

### Automatic truecolor detection

Nvim 0.10 will now automatically determine if the terminal emulator supports
24 bit color ("truecolor") and enable the `'termguicolors'` option if it does.
It does this through a combination of heuristics (`$COLORTERM`, terminfo) and
terminal queries (DECRQSS, XTGETTCAP). This detection works even over SSH
connections and when inside a terminal multiplexer such as `tmux`.

## LSP inlay hints

Include screenshot, picture is worth a thousand words
Nvim 0.10 now supports [LSP inlay hints][#23984] thanks to [Chinmay
Dalal][@p00f]. A picture here will do more than my words can:

Credit: Chinmay Dalal ([@p00f][])
{{< figure src="/img/nvim-inlay-hints.png"
           alt="Screenshot of Nvim showing inlay hints" >}}

PR: https://github.com/neovim/neovim/pull/23736
The dark colored texts which display type annotations for variable declarations
are inlay hints. This text is not part of the actual source file in the
buffer, but is "virtual" text inserted by Nvim and provided by the language
server. These hints can be enabled or disabled dynamically using
`vim.lsp.inlay_hint.enable()`.

Many other new LSP features were added in Nvim 0.10 as well. Refer to the
"LSP" section in `:h news` for a full list.

[#23984]: https://github.com/neovim/neovim/pull/23984
[@p00f]: https://github.com/p00f

## Tree-sitter query editor

"If you didn't already know about the Tree-sitter inspector..."
Nvim 0.10 adds even more tools for working with Tree-sitter queries. If you
didn't know already, Nvim bundles an "inspector" which allows you to view the
abstract syntax tree of any source file with the `:InspectTree` command (so
long as a Tree-sitter parser for the file's language is installed). Example:

{{< figure src="/img/nvim-inspect-tree.png"
           alt="Screenshot of the :InspectTree command in Nvim" >}}

You can edit queries and see the results live.
Thanks to [Maria José Solano][@MariaSolOs], Nvim 0.10 adds a powerful
capability to the Tree-sitter inspector: [a query editor][#24703]. The query
editor allows you to write queries and see the matches in a source buffer in
real time. Being able to create and modify queries interactively makes writing
new queries a breeze. Example:

"Neovim is the best tool for working with Tree-sitter, even if you don't use
Neovim".
{{< figure src="/img/nvim-query-editor.png"
           alt="Screenshot of the :EditQuery command in Nvim" >}}

:InspectTree
Notice that the text that is matched by the query is highlighted in the source
buffer and that the text **identifier** (the capture group I used in my query)
is floating on the line next to the match. As I update my query in the editor,
the corresponding highlights in the source buffer change in real time.

:EditQuery
The query editor can be opened by pressing `o` in the `:InspectTree` window,
with the `:EditQuery` command, or by calling `vim.treesitter.query.edit()`
directly.

Credit: Maria José Solano ([@MariaSolOs][])
With `:InspectTree` and `:EditQuery`, Neovim is one of the best tools (if not
_the_ best tool) for working with Tree-sitter, even if you don't actually use
Neovim.

[#24703]: https://github.com/neovim/neovim/pull/24703
[@MariaSolOs]: https://github.com/MariaSolOs

## Miscellaneous

As I mentioned at the top of this post, there are _a lot_ of new features in
this release, and I am not going to cover all of them. Here I'll list a few
more that I personally think are worth mentioning:

* The `:terminal` command now accepts modifiers, so you can use e.g. `:botright
  terminal` (or `:bo te`) to open a new terminal window in a split at the
  bottom of your screen. In addition, `:terminal` buffers that are started
  with no arguments (and thus open a shell) will close automatically when the
  shell exits without an error.

* `gx` in Normal mode calls `vim.ui.open()` on whatever is under the cursor,
  which shells out to your operating system's "open" capability (e.g. `open`
  on macOS or `xdg-open` on Linux). For instance, pressing `gx` on a URL will
  open that URL in your browser.

* The LSP client capability `workspace/didChangeWatchedFiles` is enabled by
  default. This may cause performance issues on Linux due to limitations with
  the file watching API in libuv. For best results on Linux, install
  `fswatch`. If installed, Nvim will use `fswatch` to implement the file
  watching capability automatically.

* `Q` and `@` in Visual mode will execute the last record/executed macro for
  all visually selected lines.

* Users using a terminal emulator that supports the Kitty keyboard protocol
  can create mappings using the "super" and "meta" modifiers with the `<D-`
  and `<T-` prefixes, respectively (e.g. `<D-S>` is `Cmd+S` on macOS).

<!--
## New 'winfixbuf' option

It often happens that a Nvim user or contributor first adds a new feature to
Vim (Nvim's "upstream") and, if when it is accepted in Vim, ports it to Nvim.
Vim (Nvim's "upstream") and, if it is accepted in Vim, ports it to Nvim.
That is what happened with the `'winfixbuf'` feature, which was implemented
first in [Vim][vim#13903] and later ported to [Nvim][nvim#27738], both by the
same contributor (GitHub user [@ColinKennedy][]).

This feature ....
This feature forces a buffer to "stick" to a certain window and displays an
error if any command or motion would cause the window's buffer to change. This
is useful for things like terminal windows, when you may want a single window
to only ever display a `:terminal` buffer, or for special "status" windows
created by plugins (e.g. vim-fugitive's `:Git` command).

[vim#13903]: https://github.com/vim/vim/pull/13903
[nvim#27738]: https://github.com/neovim/neovim/pull/27738
[@ColinKennedy]: https://github.com/ColinKennedy
-->

## Roadmap

The Neovim project is loosely organized and structured. We follow a "fun
driven development" paradigm: for the most part, contributors and maintainers
work on things that are personally interesting to them. Because of this, it
can be difficult to predict what will happen in future releases. If there is a
feature you want to see implemented, the best way to do it is to take a crack
at it yourself: many of the features mentioned in this very blog post were
contributed by users that are not part of the "core" maintenance team!

There is active chatter about further improving the LSP and Tree-sitter
experience (as mentioned above, builtin snippet and completion support are a
work-in-progress). One of the biggest challenges with Tree-sitter is parser
distribution: currently, parsers are shared object files which must be
compiled on every user's machine or distributed with a system package manager.
We are already working on implementing the new [Tree-sitter WASM
capabilities][#28415] which will enable distributing Tree-sitter parsers as
portable WASM blobs. This solves the distribution problem and may enable
Neovim to ship more Tree-sitter parsers out of the box.

We would also like to integrate some of the functionality from
[nvim-lspconfig][] so that, ideally, nvim-lspconfig is just a "bag of configs"
without any smarts or core logic. How best to do this is still hotly debated,
but it is something that is being discussed.

[#28415]: https://github.com/neovim/neovim/pull/28415

## Getting Involved

There is nothing quite as fun as hacking on your own tools. If you are a
Neovim user, I encourage you to get involved, whether that is through
contributing directly to the Neovim project or a plugin, or simply
participating in community spaces such as the [Neovim Matrix room][]. If you
have pain points or frustrations when using Neovim, please let us know. Many
of us on the core maintainance team have been using Vim/Nvim for so long that
we've forgotten what it's like to be a beginner and, speaking for myself at
least, this can leave blind spots on how things can be improved.

Thanks for reading and for using Neovim! Hopefully the next update will come a
little sooner.

[Neovim matrix room]: https://matrix.to/#/#neovim:matrix.org

A static/img/nvim-colorscheme-new.png => static/img/nvim-colorscheme-new.png +0 -0
A static/img/nvim-colorscheme-old.png => static/img/nvim-colorscheme-old.png +0 -0
A static/img/nvim-inlay-hints.png => static/img/nvim-inlay-hints.png +0 -0
A static/img/nvim-inspect-tree.png => static/img/nvim-inspect-tree.png +0 -0
A static/img/nvim-query-editor.png => static/img/nvim-query-editor.png +0 -0
A static/img/nvim-readme.png => static/img/nvim-readme.png +0 -0