fixup! news: 0.5.1

Author: justinmk

Diff for: _posts/2021-09-26-newsletter.md

@@ -1,22 +1,23 @@
 ---
 layout: newsletter
-title: "Neovim News #12 - The Work Continues"
+title: "Neovim: The Work Continues"
 category: newsletter
 permalink: /news/2021/09
 ---
 
-> The Citadel stripped me of it. They found some of my... experiments... too bold.
->
+> The Citadel found some of my... experiments... too bold.
 > —Qyburn
 
-Nvim 0.5.1 has been released, it includes many fixes and some breaking changes:
+Nvim 0.5.1 has been released, it includes many fixes and some **breaking changes**:
 
-- ...
-- ...
+- changed LSP handler signature: https://github.com/neovim/neovim/pull/15504
+- renamed `vim.register_keystroke_callback` => `vim.on_key`
+
+These breaking changes are part of the 0.5.1 maintenance release to avoid delay while we develop 0.6.
 
 ## Velocity
 
-Lua-first development is now a central practice in the Neovim project.
+Lua-first is now a central practice in the Neovim project.
 
 We started with everything tucked into `vim.lsp`. The community began heavily
 building on `vim.lsp.diagnostic`, it became clear that this "diagnostic"
@@ -65,21 +66,25 @@ Work on [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter) pa
 
 Also, Neovim itself only provides a (Lua) API for generating and querying the syntax tree using the bundled tree-sitter library; see [`:h treesitter`](https://neovim.io/doc/user/treesitter.html). User-facing features like the ones mentioned above are implemented in plugins like XXX and XXX.
 
-## Defaults
+## Unreleased (master branch)
+
+### Virtual lines ("ghost text")
+
+- "ghost text" (virtual lines) https://github.com/neovim/neovim/pull/15351
+
+### Defaults
 
-Nvim `master` branch has implemented a new [batch of improvements](https://github.com/neovim/neovim/issues/6289) to the [editor defaults](https://neovim.io/doc/user/vim_diff.html#nvim-defaults).
+Nvim `master` branch has implemented a big [batch of improvements](https://github.com/neovim/neovim/issues/6289) to the [editor defaults](https://neovim.io/doc/user/vim_diff.html#nvim-defaults), including:
+
+- ['backupdir'](https://neovim.io/doc/user/options.html#'backupdir') now [auto-creates its directory](https://github.com/neovim/neovim/pull/15433), as the 'undodir' and 'directory' (swapfile) options already do
+- `CTRL-L` is mapped to also clear "/" search highlighting
+- ['inccommand'](https://neovim.io/doc/user/options.html#'inccommand') (live preview of the `:substitute` command) is enabled by default
+- `Y` is [mapped](https://github.com/neovim/neovim/pull/13268) to behave like `D` and `C` 🙀
 
 Having now established patterns for "default autocommands" and "default
 mappings", we will use this mechanism liberally to make quality-of-life
 improvements to `nvim -u NONE` without breaking scripts.
 
-Notable changes are:
-
-- the 'backupdir' option now [auto-creates its directory](https://github.com/neovim/neovim/pull/15433), as the 'undodir' and 'directory' (swapfile) options already do
-- `<C-L>` has a default mapping which clears `/` search highlighting
-- 'inccommand' (live preview of the `:substitute` command) is enabled by default
-- `Y` has a [default mapping](https://github.com/neovim/neovim/pull/13268) so that it behaves like `D` and `C` 🙀
-
 ## Feedback loop
 
 Your feedback helps us.  We considered removing the 'backspace' option and decided to keep it based on comments explaining the use cases for some of its non-default behavior. We also asked about `:hardcopy` and found that it's relatively unknown but still sees usage; we will not remove its implementation until we have a complete answer for inscribing your pixels to paper.