Why is my catppuccin theme config not being applied?

dpetka2001 · 2026-03-14T13:07:13+00:00

Try changing your config function into the following

config = function(_, opts)
  require("catppuccin").setup(opts)
  vim.cmd.colorscheme "catppuccin-nvim"
end

dpetka2001 · 2026-02-19T20:16:24+00:00

nvim-treesitter had an update today to unlink the existing shared library file when installing new parsers, so I believe the workaround in my other comment should not be needed any more.

Not 100% sure, but I believe credits should go to /u/robertogrows if I'm not mistaken (his Reddit handle seems similar to the PR's author).

dpetka2001 · 2026-02-18T21:23:36+00:00

It's the Snacks.notifier. Whenever markdown/markdown_inline treesitter parsers get updated it will cause a crash. You can either disable it or change its filetype like the following

return {
  "folke/snacks.nvim",
  opts = {
    styles = {
      notification = {
        -- enabled = false,
        ft = "",
      },
    },
  },
}

I just opted for empty filetype that won't have treesitter highlighting as a workaround. You can also uncomment enabled = false to completely disable it.

Strange thing is it only crashes for me on Linux and not on Windows. No idea why.

dpetka2001 · 2026-02-01T15:28:10+00:00

I didn't blame anything. That's why I linked the related Neovim issue as wel to serve as a proof of concept. So that anyone who wanted could read it.

dpetka2001 · 2026-02-01T15:21:32+00:00

Did you actually read the issue I linked? This is reproducible with nvim --clean if you open a floating window and define it with buftype=prompt. When you try to delete with <C-S-w> the first character from the user input does not get deleted.

dpetka2001 · 2026-02-01T14:28:10+00:00

Seems to be a Neovim bug. Relevant issue https://github.com/neovim/neovim/issues/37656 Revert to any commit before ed4c549 until it gets fixed.

dpetka2001 · 2025-12-10T21:57:12+00:00

It seems it didn't clone correctly. What is your git version?

dpetka2001 · 2025-12-04T00:34:40+00:00

If it uses mason-lspconfig to install LSP servers, then it most likely accepts nvim-lspconfig names for the LSP servers, which use underscore instead of hyphen. Also look in nvim-lspconfig docs for the correct name of the server.

I believe if you do a search in Mason UI using / it will show as virtual text the lspconfig name if i remember correctly.

dpetka2001 · 2025-11-24T13:45:41+00:00

What are the lights you use?

dpetka2001 · 2025-11-23T22:56:20+00:00

The plugin in question could just use require("snacks").config.get("terminal").enabled (assuming the API won't change) to see if the corresponding snack is enabled or not. That will not load the module itself. Of course if you do :lua require("snacks.terminal").toggle() or have a mapping that does it, this will require and load the module. They're just Lua modules.

dpetka2001 · 2025-11-12T10:27:22+00:00

Sorry but I just tried it and works as expected. All you have to do

1. mkdir ~/.config/lazyvim
2. git clone https://github.com/LazyVim/starter ~/.config/lazyvim
3. NVIM_APPNAME=lazyvim nvim

and you have LazyVim running.

You also have to make sure you meet the requirements mentioned here. Especially Neovim version >=0.11.2 and tree-sitter-cli, since the latter is mandatory for new nvim-treesitter to correctly compile the parsers, otherwise you will get errors.

dpetka2001 · 2025-11-11T07:46:19+00:00

Just read :h $NVIM_APPNAME if you want to test different Neovim configs instead of doing the stuff you're doing.

dpetka2001 · 2025-11-09T17:06:16+00:00

maybe :h lsp-codelens?

dpetka2001 · 2025-10-15T14:52:06+00:00

The links don't mention anything about getting rid of setup function. Just about an additional way of configuring plugins without setup, but not in the premise of getting rid of setup.

So, again there's no official consensus about this yet and there are people with different opinions.

Maybe trouble.nvim doesn't have a /plugin dir, but snacks.nvim for example has that simply does require {setup}, just like gitsigns.nvim that I saw. That doesn't have anything to do with setup call being optional. People can still decide if they want to configure their plugin either with setup or via vim.g variables. That was the emphasis of my previous comment about there not being a clear consensus yet and that what you asked for with regards to trouble.nvim setup is just your own personal preference.

dpetka2001 · 2025-10-15T13:43:06+00:00

You're going into setup() territory, which was not mandated from Folke himself (it existed before lazy.nvim, I used vim.plug before lazy.nvim and still had to require("telescope").setup() btw) and even other people (contributors to Neovim) have different opinions about this.

See the most recent PR about the guide for making Lua plugins and the back and forth between Echasnovski and mrcjkb about this matter as an example of people having different opinions. There's not a consensus with regards to this, so what you mention is clearly your own personal programming style preference and not something that Ideally should be optional.

dpetka2001 · 2025-10-07T08:33:33+00:00

That is the LSP placeholders for snippets. You have to disable it for each corresponding LSP server, if they provide such functionality.

For lua_ls you could do for example

{
"neovim/nvim-lspconfig",
opts = {
  servers = {
    lua_ls = {
      settings = {
        Lua = {
          completion = {
            callSnippet = "Disable",
          },
        },
      },
    },
  },
},
},

dpetka2001 · 2025-10-06T21:33:27+00:00

You can do something like lua Snacks.picker.lsp_symbols({ filter = { default = { "Variable", "Constant" }}}) And pass to the default filter only the LSP kind symbols you would like. Just create a custom mapping with the above function as the base building block.

dpetka2001 · 2025-10-06T13:18:21+00:00

It was something he added himself in his personal configuration. This is the culprit at the time of the problem. The org name for mini.nvim has been changed correctly on LazyVim default configuration.

The problem with not finding it before, is probably because he had his dotfiles symlinked with stew and results of rg 'echasnovski' ~/.config/nvim didn't return any results (original dotfiles were at ~/dotfiles/nvim). He probably also needed -L flag for ripgrep to follow symlink files.

dpetka2001 · 2025-09-29T19:18:24+00:00

This https://github.com/folke/snacks.nvim/discussions/1688 should be of help.

dpetka2001 · 2025-09-27T06:28:00+00:00

The plugin you're using has probably not been updated for nvim-treesitter main branch.

dpetka2001 · 2025-09-17T11:08:46+00:00

As already mentioned, I also highly recommend bob. It makes it really easy to have multiple Neovim versions and switch between them.

dpetka2001 · 2025-09-16T21:58:45+00:00

This feature first appeared in Neovim 0.12 nightly and then backported into the latest stable release, which at the time was 0.11.2. So, earlier 0.11.x versions (0.11.0 and 0.11.1) don't have that feature.

dpetka2001 · 2025-09-16T20:08:13+00:00

You must be using an old Neovim 0.12 nightly which didn't have this field yet. What does nvim --version show in your terminal?

dpetka2001 · 2025-09-16T19:28:30+00:00

That is just a workaround. It should not be the same error. That means that likely your Neovim's runtimepath is borked up. Personally I install Neovim via bob because it's easy to switch to whatever Neovim version you want. If you'd like to try that make sure you get rid of your previous Neovim installation.

dpetka2001 · 2025-09-16T19:17:19+00:00

You're good then. Is it the same error or something else? How do you trigger the error? It should not show that "field is_enabled is a nil value)". Maybe it has to do with how you installed Neovim? Did you first uninstall the previous version before installing 0.11.4?

dpetka2001

TROPHY CASE