formatting matters

Justin M. Keyes 2021-07-03 23:37:17 -07:00
parent be4da4d5fa
commit 2de2b650da

@ -1,16 +1,13 @@
## Moved to [#14090](https://github.com/neovim/neovim/issues/14090) so that users can subscribe to get notified about updates.
<details>
<summary>Old content</summary>
The following changes may require users to update configuration, plugins, or expectations. Only **breaking changes** are mentioned here, this is not a reference for new features (see [`:help nvim`](http://neovim.io/doc/user/nvim.html) instead).
- If you don't have Neovim, see [Building Neovim](Building-Neovim) or [Installing Neovim](Installing-Neovim).
- Use `:checkhealth` to detect and fix common problems.
------------
### 2021/3/9
This page is replaced by the github issue https://github.com/neovim/neovim/issues/14090 so that users can subscribe to get notifications about **breaking** changes. Please refer to that issue now instead of this page.
<details>
### 2021/3/9
[#13875](https://github.com/neovim/neovim/pull/13875) was merged which makes it an error to use `vim.fn` to call functions in `vim.api`. For example, before this PR it was possible to call either `vim.fn.nvim_get_current_buf()` or `vim.api.nvim_get_current_buf()` to get the current buffer; now, trying to call `vim.fn.nvim_get_current_buf` results in an error that says to use `vim.api.nvim_get_current_buf` instead. Any plugins that use `vim.fn` to call functions available in `vim.api` will therefore not work until updated to use `vim.api`.