SebasCoding

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.

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.

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.

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.

GitHub - nvim-treesitter/nvim-treesitter: Nvim Treesitter configurations and abstraction layer Nvim Treesitter configurations and abstraction layer - nvim-treesitter/nvim-treesitter

To install a parser you do :TSUpdate parser, as explained here github.com/nvim-treesit...

`:grep` is my friend (or my own `:Rg` that uses ripgrep). That with the quickfix can do wonders.

Deberian funcionar bien, pero si es cierto que probablemente tengas que definir manualmente varios grupos nuevos, y al final casi terminas creando un nuevo tema. Mucho mas facil usar uno que ya existe.

Termguicolors no tiene nada que ver con treesitter. Solo va a limitar la cantidad de colores que va a mostrar tu terminal, pero treesitter va a funcionar.

Probablemente puedas usar el tema viejo si seteas 'termguicolors' a false.

As you are an emacs user and new to modal editing, did you try Evil?

Adding to my previous comment, there is a lot of new nvim users that came from vscode, so there are a lot of plugins that try to use vim as vscode (as in workflow or appearance). Not bad per se, but irrelevant to an emacs user.

I started with nvim, not vim, and sadly most nvim content (videos, blogs, etc) is around plugins, so if you don't know nvim you easily start with a lot of them. Once you start really learning vim you understand that most of them are useless for your workflow or imitations of builtins.

GitHub - boltlessengineer/NativeVim: Neovim config WITHOUT plugins Neovim config WITHOUT plugins. Contribute to boltlessengineer/NativeVim development by creating an account on GitHub.

I'm with Aaron, if you want a simpler config is very doable. Here is an example without any plugin: github.com/boltlessengi... You may want to use nvim-treesitter just for easier parsers installation. And for git you can use fugitive which I think it's similar to magit (never used emacs).

Unless css added a new syntax idk, that's not pure css. Maybe it's using some preprocessor (sass, postcss,etc). In that case you probably need to configure the lsp or use another one.

People udually tweak their config in their free time, idk how that kills prpductivity. Or people using VS code 24/7?

Exactly. I though that since you wanted it for nvim integrations that you needed the nvim directory. With the same function you can get other important directories too like data or state.

bc it's a third party program that it's preinstall in (most?) Unix systems. The (neo)vim builtin = register can do math too (and much more)

You can do `vim.fn.stdpath('config')`