SebasCoding
@sebascoding.bsky.social
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.
November 7, 2025 at 10:43 PM
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.
October 19, 2025 at 12:21 AM
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?
October 18, 2025 at 5:15 PM
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.
October 15, 2025 at 7:47 PM
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.
October 15, 2025 at 5:58 PM
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)
September 8, 2025 at 3:15 AM
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.
August 30, 2025 at 10:21 AM
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?)
August 29, 2025 at 2:39 AM
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)
August 6, 2025 at 9:10 AM
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 :)
July 17, 2025 at 9:13 AM
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.
July 16, 2025 at 8:25 PM
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.
July 16, 2025 at 8:15 PM
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.
July 16, 2025 at 8:01 PM
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.
PS: llms really make that kind of comments, so new devs may think that's how you should do it.
June 27, 2025 at 11:16 AM
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.
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.
June 27, 2025 at 10:59 AM
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.
May 28, 2025 at 7:09 AM
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.
What would be the diference with `exrc` and `.nvim.lua`?
May 5, 2025 at 1:25 AM
What would be the diference with `exrc` and `.nvim.lua`?
Understandable, names are very similar and it is confusing.
April 5, 2025 at 11:07 AM
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.
April 5, 2025 at 1:38 AM
You are confusing lazy.nvim package manager with LazyVim nvim distribution. The package manager doesn't set any config or keybindings.
That's not a minimal config at all, there are even some superfluous plugins (like, why two plugins for testing and two code runners?). It's not a neovim problem is I install 100 plugins and call it minimal.
March 31, 2025 at 5:57 PM
That's not a minimal config at all, there are even some superfluous plugins (like, why two plugins for testing and two code runners?). It's not a neovim problem is I install 100 plugins and call it minimal.
Option 1: Change indent formatting and make a new commit.
Option 2: Add a "I'm alive" message at the top of the readme.
Option 2: Add a "I'm alive" message at the top of the readme.
March 24, 2025 at 1:33 AM
Option 1: Change indent formatting and make a new commit.
Option 2: Add a "I'm alive" message at the top of the readme.
Option 2: Add a "I'm alive" message at the top of the readme.
I recommend to use the nvim-jdtls plugin, the best nvim experience with Java.
March 16, 2025 at 12:52 AM
I recommend to use the nvim-jdtls plugin, the best nvim experience with Java.
I don't understand the issue. You just need to use one plugin manager.
March 11, 2025 at 8:19 PM
I don't understand the issue. You just need to use one plugin manager.
Oh, that's a different beast. Do you made the parser? My respects. Was going to suggest something but just saw you already made the pr.
March 6, 2025 at 12:44 AM
Oh, that's a different beast. Do you made the parser? My respects. Was going to suggest something but just saw you already made the pr.