this post was submitted on 07 Sep 2023
41 points (100.0% liked)

Neovim

1726 readers
1 users here now

Neovim is a modal text editor forked off of Vim in 2014. Being modal means that you do not simply type text on screen, but the behavior and functionality of the editor changes entirely depending on the mode.

The most common and most used mode, the "normal mode" for Neovim is to essentially turn your keyboard in to hotkeys with which you can navigate and manipulate text. Several modes exist, but two other most common ones are "insert mode" where you type in text directly as if it was a traditional text editor, and "visual mode" where you select text.

Neovim seeks to enable further community participation in its development and to make drastic changes without turning it in to something that is "not Vim". Neovim also seeks to enable embedding the editor within GUI applications.

The Neovim logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 3 years ago
MODERATORS
 

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

all 13 comments
sorted by: hot top controversial new old
[–] vext01@lemmy.sdf.org 11 points 1 year ago (5 children)

Wait, packer is dead? Feels like I've been through 100 damned packed managers.

What should one use now then?

[–] skipperwannabe@lemm.ee 7 points 1 year ago* (last edited 1 year ago)

The notice on packer suggested to use either lazy or pckr

NOTICE:

This repository is currently unmaintained. For the time being (as of August, 2023), it is recommended to use one of the following plugin managers instead:

lazy.nvim: Most stable and maintained plugin manager for Nvim.

pckr.nvim: Spiritual successor of packer.nvim. Functional but not as stable as lazy.nvim.

[–] ck_@discuss.tchncs.de 5 points 1 year ago (1 children)

As long as it still works for you, there is no need to switch. Resist the urge to follow the hype, it just means you'll spend less time doing something actually productive.

[–] ptrckstr@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 children)

Lazy has a reference how to migrate to it, also this YouTube video is pretty helpful

[–] tun@lemm.ee 1 points 1 year ago

Specifically lazy.nvim migration guide has guides for packer and paq.

[–] Slotos@feddit.nl 2 points 1 year ago

Been using minpac since forever. It has all the minimal functionality and is a perfect dead project one doesn’t have to worry about.

One day I might switch to lazy, but so far I’m too lazy to.

[–] tubofboldts@lemm.ee 1 points 1 year ago

Yeah I’ll stick with packer until some breaking change maybe happens with neovim in the future. I say this with no knowledge of the other two options, but everything with packer is so damn easy I can’t imagine lazy or pckr being any easier.

[–] Cube6392@beehaw.org 2 points 1 year ago
[–] skipperwannabe@lemm.ee 2 points 1 year ago (2 children)

Considering null-ls still works on nightly, it should be fine.

[–] tun@lemm.ee 1 points 1 year ago

LazyVim migrated to nvimtools/none-ls

[–] deriver@fosstodon.org 0 points 1 year ago (1 children)

@skipperwannabe

Does "still works" mean null-ls works just as well today on Neovim v0.9.2 (and/or latest nightly) as it did on Neovim v0.9.1 when the null-ls archival announcement was made about two months ago or that it "still works" as long as you can work around issues stemming from a change(s) to Neovim since the null-ls archival announcement?

Since Neovim v0.9.2 "is a maintenance release, focused on bug fixes and performance improvements", I assume its the former.

[–] skipperwannabe@lemm.ee 1 points 1 year ago

For me, it works as well on nightly without any modifications as it did when the archival announcement was made. But I only use formatters and one or two linters. So can't confirm for other features.

That said, I am thinking about changing to conform.nivm for formatting.