Neovim v0.9.2 is now available

This is the first Neovim release since Bram Moolenaar passed away and the archival/deprecation of both null-ls.nvim and packer.nvim.

Is anyone running into any issues with this release (particularly if you use null-ls or packer)? How are the Neovim distros (eg - NvChad, AstroNvim, LazyVim, LunarVim, etc.) performing after the update?

https://github.com/neovim/neovim/releases/tag/v0.9.2

#nvim #Neovim #NvChad #AstroVim #LazyVim #LunarVim

@neovim

Lo and behold, LazyVim, forsooth! For I am of a slothful nature, reluctant to toil, and unwilling to exert mine energies.

#LazyVim #Vim #IDE

Just discovered #Lazyvim (a #Neovim config)... It looks like it has the file sidebar I like out of the box, completions working (how the hell?!), super fancy notification boxes (ehh) and floating command line, and it was dead simple to install. Now to get into configuring it (change the theme, font size, put the command bar near the bottom, etc), and hell let's start using it for something!

Considering #LazyVim after hearing about it from @changelog today. I've maintained by own vim config for a long time but I can already see a lot of overlap with LazyVim.

There's a strong argument to save time and pool the effort on maintaining a good IDE setup, plus benefit from the community's knowledge.

LazyVim: https://www.lazyvim.org/
#linux #foss #config #vim #lazyvim

@jiristefka I tried #LazyVim, then I read all the source code to understand what it was doing and created my own simpler DIY config with just the parts I wanted. Both AstroVim and LazyVim feel like better starting points than an empty config file.

The new standard for text editor features is VS Code and that it takes a lot of #NeoVim plug-ins to match that.

Noob here, need some #neovim help.

I want to use nvim (#lazyvim) on my work windows machine by running the .exe from the Downloads folder (I don't have admin permissions so I think I can't install it in the usual folder)

The problem is that when I try to "find files", it can only look inside its own folder (C:\User\Downloads\nvim-win64). Is there any way to make it find other folders?

Also I'd like a VSCode-like experience, where I can open a folder as a project workspace. Is that possible?

@oobleck couldn’t agree more!

Yeah I tried both #Helix and #Zed briefly but I’ve definitively settled for #Neovim (#LazyVim) for the same reason you mention.

For some very few tasks I still switch to vscode, where e.g. the Pylance LSP in vscode is more mature/advanced than Pyright when doing larger refactorings.

My battery life on the Apple MacBook Pro M1 is so-so, because of using the #Arc browser. I hope they can fix that drain…

Ok ok #10ThingsILikeRightNow in random order

1) Discovering new Distro's (#Void & #NixOS specific)
2) Conversing on the #Fediverse (#Fosstodon.org mostly)
3) #Smarthome (#HomeAssistant)
4) #LazyVim (#NeoVim in general)
5) #Qutebrowser
6) #Tut for Mastodon
7) Seeing my daughter grow up (7yo)
8) #Wayland
9) #Hyprland (even if i'm using Sway(FX) now)
10) Does 1 count as 2?

It's taken me more than a month to fully transition from vscode to Neovim... but now I'm starting to feel fluent, thanks to #LazyVim - and it's such a nice experience!

I've made one big deviation from most common setups you see out there for git/diffs and that is to skip #Fugitive and instead go for #LazyGit and the extremely underrated #Diffview.

The only thing I'm missing right now is some Pylance refactoring magic.

I should probably write a blog post about my new setup at some point!

Bit of a major change in direction with my #neovim config today. Been gradually building up my own config for weeks, but realised that I'm simply heading towards having a setup similar too, but not as good as, #LazyVim

Decided to switch to using LazyVim and just maintain my modifications to it instead. Going to take a little while to figure out the default keybindings, but it seems seriously slick!
https://www.lazyvim.org/

@michael_jaeger @refnode
Thanks for pointing this out, "nvim config refactoring weekend" is one reason I'm keeping an eye on #HelixEditor. Gonna give #LazyVim a go in the meantime.

As an aspiring #neovim convert I'm wondering how you deal with (GitHub PR) code reviews...

Do you review the diffs inside of Neovim and if so, do you use any fancy plugins for it?

I've found diffview that seems to work well: https://github.com/sindrets/diffview.nvim

Then there's Octo which is centric to GitHub PRs: https://github.com/pwntester/octo.nvim

Would love any input on how you deal with reviews in neovim!

#LazyVim #GitHub

Is there out there any #lazyvim user or #neovim notify plugin user that faces the problem I've described in https://github.com/rcarriga/nvim-notify/issues/183 ? I'm facing it every single time I'm saving a file and changing to my next #vim window while the notification is displayed 🤯

Una vez más reescribiendo mi configuración de
#neovim , a ver si ya me convenzo. 100% #lua y un porrón de plugins, de momento con #packer después ya migraré a #lazyvim.

#vim #ide #development

Ramping up my #Neovim game trying to get pytest nicely integrated into #LazyVim. Is #Neotest the way to go?

Anyone have any #dotfiles on this they’d like to share?

This week, I jumped ship from #vim with a fairly well customized .vimrc, to #neovim with a few tweaks on top of the #LazyVim setup, and I’m ashamed to admit that the overall experience has been great so far. Kinda wish I had done this sooner.

Got myself set up on #lazyvim yesterday, so far so good. All the practice I've done with vim bindings in VSCode is paying off

@AstraKernel Instead of using kickstart.vim for your initial setup I would highly recommend #LazyVim instead.... makes a much more complete and nice IDE experience for #neovim https://github.com/LazyVim/LazyVim

#lazyvim - something is wrong, it uses 410 megabytes of memory, vs 200 megabytes vscode - including shared memory. but i like #vcpkg