Adding opts recursive_run to fix the error 'no Go files in /path/project.' This issue is caused by a recent change in the 'nvim-neotest/neotest-go' project, which now [defaults to non-recursive behavior](https://github.com/nvim-neotest/neotest-go/pull/72)
* feat(lang): add support for helm chart templates
* fix(helm): stop yamlls and disable autostart
* fix(helm): stop yaml & docker compose lsp on helm file types
Revert disabling `autostart` since that kills the LSP globally even when
opening a standard yaml file, like GitHub Workflow file.
* fix(helm): remove docker compose lsp overrides
Since docker compose LSP does not seem to be triggered or started by
opening *.yaml helm files, the config overrides were removed to simplify
Helm config.
* fix(helm): ensure mason installs helm lsp
Avoid lowering timeoutlen when running in VS Code, to avoid
unwanted timeouts from key mappings.
The lower value of 300ms (down from Neovim's default of 1000ms)
works great outside of VS Code, where it helps trigger the which-key UI
quickly, and where which-key prevents timeouts from occuring.
But in VS Code (where which-key isn't applicable), the lower value
makes it difficult to perform some key mappings in time,
such as `]p`, which requires shifting hand position.
For example, 'buffer' source by default has group_index = 2 [1], however
if we take all the sources plus crates and run them through
cmp.config.sources() again, since it's a one-dimensional list, all
group_indexes will be reset to 1.
[1] 879e29504d/lua/lazyvim/plugins/coding.lua (L74-L80)
* feat(toggle-diagnostics): change logic based on `vim.diagnostic.is_disabled`
After discussion in #2215, I thought maybe it would be beneficial if we
could change the logic of the `toggle-diagnostics` function based on if
the user has disabled diagnostics in his own configuration.
* feat(toggle-diagnostics): revert to `enable` instead of `status`
* fix(toggle): use vim.diagnostics enabled state when possible
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
3 hides all concealed text, even if there are replacement chars defined
e.g. : for Markdown, 3 hides list item markers, dots for asterisk lists
and em-dashes for dash lists
If replacements are defined as defaults in a plugin, the "Laziest™"
config would seem to be displaying them.
Level 1 only seems useful when alignment really matters.
* fix(typescript): don't hardcode values in lua table
When a user changes `vim.opt.shiftwidth` with some auto-command, it's
not taken into account. Make `opts` a function, so that values get
evaluated when `lspconfig` loads instead.
* fix(typescript): remove format settings entirely
* fix(typescript): add back comment and Lua annotations
* fix(typescript): bring back function call completion snippets
