Iordanis Petkakis

You could do something like ```lua autocmd("LspAttach", { group = augroup("no_words_python", {}), desc = "No words in Python", callback = function(ev) if vim.bo[ev.buf].filetype == "python" then Snacks.words.disable() end end, })...

This is `nvim-lspconfig`'s `vim.schedule_wrap()` in effect. Reverting https://github.com/LazyVim/LazyVim/commit/75a3809e15a0ecff9adc46c6cd3aaac51d99b561 makes it behave correctly. I believe #6456 should not be solved by LazyVim. It's the user's responsibility to work around the new...

In my personal opinion as a just a simple user like you, I believe this is a bad approach. The correct approach as you yourself have also mentioned, would be...

Vanilla Neovim itself recognizes `.env` files as `ft = sh`. LazyVim just extends the default behavior to further include additional patterns `.env.whatever`. What you want can also be achieved by...

Why would users' custom configuration be lost? When I tried it, I just configured it exactly like `nvim-cmp`. It's `nvim-cmp` itself under the hood for the most part if I...

I believe if you set `ttl = 0` it should do what you want.

It defines the amount of time the cache will be preserved if I'm not mistaken.

That's probaly how it works. It must have an autocmd that does this. No idea.

When Neovim is resized then the Dashboard gets updated. That means the sections will be recalculated and the terminal section will run the command again. With `ttl = 0`, that...

> Which means when it recalculates size and sections, then the command should not run again. I don't believe that's possible with how the current Dashboard is implemented. Of course...