Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neovim 0.12.0

github.com

Post reply on HN
Print view View original

81–90 of 271 posts

Re: Neovim 0.12.0

#81

Post by gorjusborg »

imjonse wrote: post #62

It probably goes against Vim tradition, culture and freedom to choose, but I wish they added even more built-in features (like Helix) that are currently implemented in competing and sometimes brittle plugins and have to be put together into also competing vim starter packs and distros of plugins and config files just to have a modern setup out of the box.

I agree in principle that absorbing the best from the ecosystem is good. However, anything pulled into core should have a long lifetime and be considered part of the API. This deserves careful consideration, and plugins work really well until it is clear there is a reason to pull something in.

Re: Neovim 0.12.0

#82

Post by Zizizizz »

toisanji wrote: post #28

Is anyone using them vim with Claude or any of these coding tools? I want to, but I haven’t found a good workflow.

Yes tab split, neovim on the left, companion on the right, or different tabs. The plugin codecompanion.nvim is also great. I use it for common tasks. Like:

vaf (visual around function) ad (leader key add docstring).

And it documents the functions with my system prompt instructions for what good docstings should look like.

Re: Neovim 0.12.0

#84

Post by QuantumNomad_ »

augusto-moura wrote: post #67
imjonse wrote: post #62

It probably goes against Vim tradition, culture and freedom to choose, but I wish they added even more built-in features (like Helix) that are currently implemented in competing and sometimes brittle plugins and have to be put together into also competing vim starter packs and distros of plugins and config files just to have a modern setup out of the box.

I believe neovim started as a fork specifically to implement features like LSP support and package management, VIM eventually also caught up. But i don't believe anything is out of the table, or against Vim tradition. Which features do you want to see built-in, specifically?

I’m also pretty sure that on an episode of The Standup, one of the Neovim core maintainers TJ DeVries (Teej) said that it is a good idea to prove new ideas in the form of a plugin rather than submitting pull requests for Neovim itself with new ideas that have not yet been tested out and proven in the real world. Implicitly implying that indeed Neovim is open to bring features from plugins into core Neovim itself, if they are proven to be useful for a lot of people.

Unfortunately I don’t remember what episode it was or even if it was specifically on an episode of The Standup, or if it was some other video that he and ThePrimagen did outside of The Standup.

Re: Neovim 0.12.0

#85

Post by bheadmaster »

imjonse wrote: post #62

It probably goes against Vim tradition, culture and freedom to choose, but I wish they added even more built-in features (like Helix) that are currently implemented in competing and sometimes brittle plugins and have to be put together into also competing vim starter packs and distros of plugins and config files just to have a modern setup out of the box.

This is what happened with the Language Server Protocol.

Prior to 0.9 (if I recall correctly), you had to install a plugin to be able to interface with LSP servers, and in 0.9 they integrated the support into NeoVim itself.

Re: Neovim 0.12.0

#86

Post by vermilingua »

c-hendricks wrote: post #7

I unintentionally ran the main branch when testing some changes and a lot of my config broke (mostly around LSPs, CodeCompanion was much slower streaming its responses) so might wait a bit before upgrading.

The lspconfig depreciation was a very painful upgrade for me too, as it seems to be very poorly documented; but ultimately it came down to moving all of the LSP server configuration to `vim.lsp.config` blocks, then calling `vim.lsp.enable` with all the servers I use.

I’m still not clear on what Mason is doing in my config after the switch but oh well.

Re: Neovim 0.12.0

#87

Post by dizhn »

eviks wrote: post #54
helterskelter wrote: post #19

Up next for 0.13: multiple cursors! I have no idea what I'd do with this feature but it sounds intriguing. https://neovim.io/roadmap/

You'd do text editing with it with the coolest feedback loop - immediately seeing the changes and what those changes apply to beforehand, that's different from having to repeat some macro multiple times

Highlighted search/replace does this pretty well too.

Re: Neovim 0.12.0

#88

Post by justinmk »

vermilingua wrote: post #86
c-hendricks wrote: post #7

I unintentionally ran the main branch when testing some changes and a lot of my config broke (mostly around LSPs, CodeCompanion was much slower streaming its responses) so might wait a bit before upgrading.

The lspconfig depreciation was a very painful upgrade for me too, as it seems to be very poorly documented; but ultimately it came down to moving all of the LSP server configuration to `vim.lsp.config` blocks, then calling `vim.lsp.enable` with all the servers I use. I’m still not clear on what Mason is doing in my config after the switch but oh well.

It's documented here (with migration steps):

https://github.com/neovim/nvim-lspconfig#important-%EF%B8%8F

and in a pinned issue.

and nvim-lspconfig :help has a migration guide:

https://github.com/neovim/nvim-lspconfig/blob/16812abf0e8d81...

Re: Neovim 0.12.0

#89

Post by luxurytent »

camgunz wrote: post #75
wilkystyle wrote: post #57

Earlier quoted context omitted.

dot repeat is the wrong comparison. A closer one would be macros, but even then a good multiple cursors implementation is often faster, more intuitive, and requires less cognitive overhead. One of the better examples of the usefulness of multiple cursors is from Emacs Rocks (link goes to 0:23): https://m.youtube.com/watch?v=jNa3axo40qM&t=23s

What do you when the things you want to change don't all fit on the screen at once?

You do a search/replace which has a similar function, although applied differently.
Post reply on HN