I would love to know how "a plugin got archived" translates into "change text editor one hour later"

Or you must review every commit of every editor to be 100% sure. And I don't like LLMs, I barely use them at work. But I don't understand how people can be so angry for people (that even work for free) using a tool for just 3 prs in more than 3500 commits in the last year.

There are only 3 neovim prs merged with the "AI assisted" label (and 8 closed), none of them vibe coded. And you only know about them because they are being labeled. Apparently transparency is a bad thing now. If you are only going to use an editor without any LLM code you can use nano I guess.

The best new feature in 0.12 Works great!

I think so. Works in help pages too. And it maps to document symbols if you have an active ls.

If you use nvim 0.11,you can just do `gO`, no plugin needed

So what "most professional devs have free access to pretty good modern hardware. Also the most hardcore nvim users I know own the best hardware." means? Devs have potato botebooks. Thinking that performance is not an issue because you can have a better pc is what's making software so bad.

Yeah, most devs in the world have free access to modern hardware, sure. You are delusional. Do you know there are great devs in third world countries? I definitely have an old notebook that can browse the internet without issues but can't open android studio or a big ide.

It's not weak, it is very reasonable. If you have a mac with an M5 then it probably doesn't affect you, but that doesn't mean the argument is weak. For many people, with old notebooks, that need to run an IDE, a server and maybe even docker or an emulator, performance is key.

`:term` ?

Why? Autopairing is very annoying, I hate it. I don't want my editor to insert stuff I don't write myself. What some may think is essentials others may think it's the opposite. That's why neovim maintainers don't add every feature. And in 2025 it's just one line to add your own autopairing.

Ohh, and you decided to do it voluntarily on a friday morning? Wild. The new branch is way better, but needs a lot of changes. You are brave.

A quick note, nvim-treesitter can't break as it happened to you if you don't manually change the branch, master is still the default. Is this a nix thing that changed the branch? Or are you using a distro?

I understand the appeal, even if it's not appealing to me.

Vim and Neovim have dozens of plugins that do that. Leap.nvim, flash.nvim, mini.jump2d and many others. There are some in vimscript if you prefer, just don't remember the names but should be findable.

Neovim has a snippet module that can expand them. Here is a very simple implementation that just works: github.com/boltlessengi... (idk why it was removed, I use it everyday and there is no issue with it)

The simpler way to achieve this is with dot repeat and `:h gn`, which is the same as multicursors but backwards. You first do one edit and then repeat for the next occurrence (instead of first selecting and then editing). If it's a complex edit, then macros is a better complex solution.

Those are `:h vim.lsp.inlay_hints` and have been available in neovim since 0.10 at least (maybe 0.09?)

Why not disable the checker in the lazy.nvim config? It is even disabled by default. (lazy.folke.io/configuration)

I guessed right, you use a distro. That's why you don't know how to fix your config, because it is not yours. You are complaining about LazyVim, not neovim, you just don't know the difference. And to setup my 20 plugins you just need to open the readme and copy the setup in 15 of them :)

I can work everyday with just 20 plugins, and could even delete a few more that I barely use. Doesn't look like many plugins to me. You don't like neovim, it's ok, use another thing. But I feel weird to say something is bad because I don't like something else.

If you have to look for a thousands files to find in which one you setup neotree, that's a you problem. Or maybe you use a distro and it's a distro problem. You can't blame neovim because your configuration is not organized. It's like saying a course is bad because your notes are bad.

What has neovim to do with a plugin configuration? I doubt you have "thousand configuration files" for neotree.

Comment doesn't mention type, I don't understand the code now.

PS: llms really make that kind of comments, so new devs may think that's how you should do it.

Read the comments. One uses the output of git diff and git log as the git commit message.

Setting treesitter highlighting turns syntax off by default. If you had it on you probably set `additional_vim_regex_highlighting` to true in your nvim-treesitter configuration.

Now do gg=G

What would be the diference with `exrc` and `.nvim.lua`?

Understandable, names are very similar and it is confusing.

You are confusing lazy.nvim package manager with LazyVim nvim distribution. The package manager doesn't set any config or keybindings.