Hacker News Reader

Comment by rosetremiere | Hacker News Reader

I'm using neovim with Coc (often does not work as I want it to) and ALE and friends, and it's getting sort of frustrating. It's lots of fiddling with the vimrc, each year a new better extension that I can never make work, etc. What I'd like is some editor that integrates LSP, treesitter, FZF and friends so I don't have to configure everything, while still having the modal+command model of vim. Recently there was an editor that seemed to fit the bill (I think called Hex), but it seems those "keyboard oriented" editors are more usually "american keyboard oriented", in that the bindings don't make sense for non qwerty keyboards, and remapping everything is frustrating. Essentially, I think I want an full-featured IDE with vim's extensibility and modal approach.

What's the solution?

View on HN

LunarVim: A Neovim config made with sane defaults https://github.com/ChristianChiarulli/LunarVim

LunarVim will be like Spacemacs/Doom Emacs/SpaceVim, but for neovim. A distribution of useful neovim packages with sane defaults.

This project is still at its early stage and many things change rapidly. You currently cannot easily keep your custom changes in sync with LunarVim, but support for this feature is on the way.

In a few months this project should be stable enough for typical users.

Indeed, it seems to tick quite a lot of boxes. I'm a bit confused on how to make it work with my old vimrc and plugins, and it doesn't seem to support julia's lsp yet, but I'll wait a few months, and hopefully this will be the solution I was looking for. Thanks!

VS code + the popular vim keybinding/mode extension for its editor.

I love neovim and have been using 0.5 for 1/2 a year now, loaded up with all the bleeding edge LSP, treesitter, etc. stuff and I have come to the exact same conclusion. The ecosystem is just a bit too immature and fragile right now with tons of still-evolving things. The quality of each LSP varies wildly and it's a huge wild west right now figuring out the 'right' way to move configurations to lua, use a package manager for plugins, etc. You're left with a weird frankenstein state of half your tools and plugins in the new lua world, half still in the old world.. and a net loss of features and functionality as stuff is abandoned or changed in the process of moving. It's exhausting to keep up.

I've been really hopefull it's onivim. I suspect you'll have the same issue with default bindings unfortunately.

Reply on news.ycombinator.com