Around two weeks ago I started using nvim instead of vim. I never really bothered trying out nvim earlier. I used vim for almost 20 years. I started using it in my Gentoo phase and I can't say I really loved it or that I am a competent modal aficionado. I use it in because it is almost always there locally or via ssh. It was my terminal editor of choice as nowadays I prefer most of the time to use graphical editors where I can set variable width fonts. For most of the mentioned period I was looking for an alternative, but never seriously enough. Yes, the reverse movement-action key set of kakuone makes more sense, but I got used to vim and stayed with it.
So I may be allergic to a mention of vibecoding, but reading here lately about vim getting some LLM commits. That got me to thinking. I thought about a few terminal editors and remembered that I installed (but never used nvim). I checked it out and I have to say I was impressed quickly.
What I like about nvim is mostly sensible defaults. I used to have an extensive vimrc a few years in with vim, but later on I just got a simple vimrc (16 lines of set this or that). Nvim has hlsearch, preview of a substitution, sensible defaults around mouse handling. I like the colors and the style of syntax highlighting and it looks good on a white background terminal (I may be a weirdo :P). With LSP support it really is very easy to get going even further than with vim. My config is just enabling LSP for Python.
It was enough a reason for me to bother trying something else. Though I hear you and I am not perfectly happy. All in all it was a painless switch for me, but my main point about not really being happy with vim, just invested, still means I want to switch to something else eventually. However I don't know when I will be again bothered enough to do something about it.
The two additions I'm most happy about are vim.pack and :Undotree. I've been using Mundo for years, so whether :Undotree can fully replace it remains to be seen. Having it built in is already welcome either way.
i was a huge doom emacs user for years and I got tired of trying to bring my editor to remote boxes. doom emacs had a huge install process that was really slow, so i switched t neovim and can have an editor setup on a new dev VM in minutes.
I still use emacs for various things, sometimes its org, sometimes its dired, sometimes its that random key sequence I dunno how to do anywhere else...
jmtd | 15 hours ago
One of changelog or NEWS would probably be a more interesting link for lobsters, imho.
FrostKiwi | 8 hours ago
OMG finally.
hawski | 15 hours ago
Around two weeks ago I started using nvim instead of vim. I never really bothered trying out nvim earlier. I used vim for almost 20 years. I started using it in my Gentoo phase and I can't say I really loved it or that I am a competent modal aficionado. I use it in because it is almost always there locally or via ssh. It was my terminal editor of choice as nowadays I prefer most of the time to use graphical editors where I can set variable width fonts. For most of the mentioned period I was looking for an alternative, but never seriously enough. Yes, the reverse movement-action key set of kakuone makes more sense, but I got used to vim and stayed with it.
So I may be allergic to a mention of vibecoding, but reading here lately about vim getting some LLM commits. That got me to thinking. I thought about a few terminal editors and remembered that I installed (but never used nvim). I checked it out and I have to say I was impressed quickly.
What I like about nvim is mostly sensible defaults. I used to have an extensive vimrc a few years in with vim, but later on I just got a simple vimrc (16 lines of set this or that). Nvim has hlsearch, preview of a substitution, sensible defaults around mouse handling. I like the colors and the style of syntax highlighting and it looks good on a white background terminal (I may be a weirdo :P). With LSP support it really is very easy to get going even further than with vim. My config is just enabling LSP for Python.
dzwdz | 14 hours ago
If that was your reason for switching to neovim I have some bad news.
hawski | 13 hours ago
It was enough a reason for me to bother trying something else. Though I hear you and I am not perfectly happy. All in all it was a painless switch for me, but my main point about not really being happy with vim, just invested, still means I want to switch to something else eventually. However I don't know when I will be again bothered enough to do something about it.
hoistbypetard | 12 hours ago
vim-classic, a long-term maintenance fork of vim 8.x with a specific goal of avoiding LLM crap, might suit you. I find it appealing, anyway. If
is a motivator, you might also.
hongminhee | an hour ago
The two additions I'm most happy about are vim.pack and
:Undotree. I've been using Mundo for years, so whether:Undotreecan fully replace it remains to be seen. Having it built in is already welcome either way.janus | an hour ago
I just can't decide whether it is too early to switch from Plug to vim.pack. Because it does say
Does that mean it is more stable than Plug?
echasnovski | an hour ago
For regular use (install, load, update, delete), I'd say it is.
This note is more about possible future enhancement for existing non-regular use cases (like hooks, dependency management, etc.).
FrostKiwi | 9 hours ago
Went from years of Emacs to years of VSCode to Neovim. Think I'm finally happy, excited to see development so lively.
aloys | 6 hours ago
Curious, why leaving Emacs after years?
FrostKiwi | 3 hours ago
elisp never clicked for me. nvim plugin community is more alive. I liked vim motions and hardtime.nvim convinced me to switch.
sigmonsez | 4 hours ago
i was a huge doom emacs user for years and I got tired of trying to bring my editor to remote boxes. doom emacs had a huge install process that was really slow, so i switched t neovim and can have an editor setup on a new dev VM in minutes. I still use emacs for various things, sometimes its org, sometimes its dired, sometimes its that random key sequence I dunno how to do anywhere else...
bartekci | 12 hours ago
Fairly clean upgrade only where I was informed https://github.com/nvim-treesitter/nvim-treesitter-refactor was now deprecated. Moved to https://github.com/nvim-treesitter/nvim-treesitter-locals for replacement but need to better understand.
Loaded up a Go file and syntax/colour took a good 800ms to load in. Not good. Time to dive in!
ale | 15 hours ago
I was hoping multicursors would make into this release.
56 | 12 hours ago
Is multicursors a planned thing? I hadn't heard of such but it'd be cool to have
sri | 11 hours ago
Yup, although the work is far from complete apparently. Neovim publishes a roadmap btw.
ploum | 3 hours ago
They are available in Vis: https://www.brain-dump.org/projects/vis/