Neovim 0.12 !!!!

[eamonburns]

Neovim 0.12 just dropped, with a bunch of features. We should consider what makes sense to add to kickstart.

Note: Replacing lazy.nvim with vim.pack is a bigger discussion than what is meant for this issue. This issue is meant for relatively small/uncontroversial changes. Also, there is already an issue open: #1630

Here are some initial things:

• The default mappings of mini.ai clash with the new v_an and v_in mappings. This is probably just a bug with mini.ai (This is a known issue).
• The 'autocomplete' option may be a good option to enable by default. I am not sure how it would interact with blink.cmp though.
• Enabling ui2 might be a good thing to have commented out somewhere in the config. Or, maybe not 🤷‍♂️ something to think about.

[SetsuikiHyoryu]

I’m really happy with how Neovim 0.12 has turned nvim-lspconfig (0.10) and nvim-treesitter into mere configuration and parser downloaders, while also allowing me to drop lazy.nvim entirely. I heard that native APIs for blink.cmp-like functionality existed before but weren't mature enough to replace it. I'm hoping 0.12 will finally allow native APIs to replace blink.cmp as well.

[oriori1703]

The default mappings of mini.ai clash with the new v_an and v_in mappings. This is probably just a bug with mini.ai.

This seems to be known by mini.nvim and not classified as a bug.
I'm still not sure what do with because I agree with echasnovski that those are good mappings for mini.ai.
Also, I would guess that most kickstart users are already used to them (including me). Though we may need to rip the band aid anyway, so it may as well be now.

The 'autocomplete' option may be a good option to enable by default. I am not sure how it would interact with blink.cmp though.

This has already been possible using some autocmds, it is just simpler now. I think that the reasons to stick with blink.cmp from the previous discussion are still relevant, so I don't think we need to switch.

Enabling ui2 might be a good thing to have commented out somewhere in the config. Or, maybe not 🤷‍♂️ something to think about.

Is this stable enough for general use? The experimental warnings kinda make me think this is still not the time for kickstart to use it. I'm fine with waiting for 0.13 to let this stabilize a bit more (unless the consensus is that it is already extremely stable)

[oriori1703]

Also, I'm still combing through the release notes, so feel free to suggest more interesting new features 😄

[eamonburns]

Enabling ui2 might be a good thing to have commented out somewhere in the config. Or, maybe not 🤷‍♂️ something to think about.

Is this stable enough for general use? The experimental warnings kinda make me think this is still not the time for kickstart to use it. I'm fine with waiting for 0.13 to let this stabilize a bit more (unless the consensus is that it is already extremely stable)

No, it is not stable enough for general use as far as I know. I am suggesting adding a commented-out line that enables it, with an explanation about it. Something like:

-- UI2 is an experimental feature intended to replace the builtin message + cmdline presentation layer.
-- See `:help ui2`
-- It supports highlighting the cmdline as you type, and viewing the output of commands in a pager that can be interacted with like a (mostly) normal buffer.
-- To enable it, uncomment this line. It is disabled by default since it is experimental and may break.
--require('vim._core.ui2').enable({})

Since it is experimental, there is a possibility that it can break without warning, so even with the disclaimer, some people may experience breaking changes that are difficult to debug.

[rez1-dev]

We don't need nvim-lspconfig plugin. neovim/neovim#36925

@MariaSolOs's demo video

[eamonburns]

@rez1-dev - I haven't had time to watch the video yet, but if I understand it correctly, this replaces installing nvim-lspconfig with manually copying LSP server configurations from the nvim-lspconfig repo into your own configuration.

If I am correct, I don't think this would be a good idea for kickstart. While copying configuration from nvim-lspconfig into your own configuration is not very difficult, it does introduce some friction when trying to use a new LSP (it doesn't work "out of the box").

Edit: although, this would probably be a good thing to add as a comment

[rez1-dev]

nvim-treesitter got archived today.

[feketegy]

LSP is still not that easy to set up, imho, but it's significantly simpler than how it was before, so that cuts out mason and nvim-lspconfig in my book.

nvim-treesitter is still somewhat problematic to remove, but I'm in the process of doing so.

lazy is fully replaceable with the native vim pack, in the context of kickstarer of course.

blink.cmp can't be replaced with the native autocomplete, as of today, it still provides a lot of value on top of the native autocomplete.

[eamonburns]

LSP is still not that easy to set up, imho, but it's significantly simpler than how it was before, so that cuts out mason and nvim-lspconfig in my book.

Mason is used to install LSP servers, not to configure them. I don't think 0.12 affects whether Mason is needed. Removing nvim-lspconfig is still under discussion (#1971 (comment))

[oriori1703]

Another feature we can add is support for codelens.
Either by enable it default, or adding a key map to toggle it (like we do for inlay hints).