* Fix missing autocomplete in .vue files
The existing Vue extra was not properly configuring vtsls to use the globalPlugin: '@vue/typescript-plugin'
This commit fixes missing typescript autocomplete in .vue files.
* move @vue/typescript-plugin back to extend function call
* tidy LazyVim.extend() arguments
fix this warning
```
Warn 11:52:45 PM notify.warn nvim-lspconfig.rust_analyzer has been setup.
This will likely lead to conflicts with the rustaceanvim LSP client.
See ':h rustaceanvim.mason'
```
fix taken from https://github.com/mrcjkb/rustaceanvim/blob/master/doc/mason.txt
Based on [vtsls schema](bd2df5a2d4/packages/service/configuration.schema.json (L1092)), experimental setting should be vtsls property not typescript.
```json
"vtsls.experimental.completion.enableServerSideFuzzyMatch": {
"default": false,
"type": "boolean",
"description": "Execute fuzzy match of completion items on server side. Enable this will help filter out useless completion items from tsserver."
},
```
* Added R extra
* Removed "made by Ben10164"
* Formatted Lua
* Removed hardcoded addition of R-languageserver in MasonLSP
* Improved nvim-lspconfig config for r_language_server
* Added nvim-neotest
* Format
* Removed Lualine
* Rework into opts, modify `pdfviewer` to be os dependent
* refactor: r
* fix: add cmp-r back
* Added quarto whichkey group label
* Set pdfviewer to be an empty string
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
According to the maintainer of `rustaceanvim` (see his comment [here](https://github.com/LazyVim/LazyVim/pull/2198#issuecomment-1999475044)) he says
> To pick up on this: There's a good reason rustaceanvim doesn't automatically pick up a mason.nvim installation. It will most likely be built with a different toolchain than the one your project uses, often leading to discrepancies and subtle bugs.
It's easy to configure rustaceanvim to use mason.nvim if you really want it, but I generally adhere to the YAGNI principle.
I tried locally and the removal of `rust-analyzer` from `nvim-lspconfig` doesn't
seem to have any effect on how `rustaceanvim` behaves.
I propose to remove all instances of `rust-analyzer` from `nvim-lspconfig` to avoid
any possible issues from users that don't have `rust-analyzer` installed
in their toolchain (in this case it would pick up Mason's $PATH I
believe), since they will think that since `rust-analyzer` is installed
by Mason, there shouldn't be a problem and report issues as bugs.
* Add kotlin lang
* Update the opts.ensure_installed
* Add the kotlin setup in nvim-dap
* Update plugins based on the review comments.
1. Remove kotlin language server from mason
2. Add optinal is true, only enabled if the user has explicitly enabled
the extra plugin.
3. Remove duplicate dependencies cause they are already defined in the
plugin.
4. Add none-ls as optional
* Update comment message
* feat(typescript): configure inlayHint
since LazyVim have toggle inlayhint keymap, it make sense to configure
them for each extra languages provided. In this commit I just add the
configuration for typescript, since IDK how to configure the rest of
lang extras that was provided.
* fix: changed defaults
---------
Co-authored-by: Radvil <radvil.linux@gmail.com>
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
If lazy extras yaml is enabled, yamlls was being loaded not ansiblels.
Add ft = {} to nvim-ansible spec allows ft=yaml.ansible to be detected.
Re-mapped nvim-ansible plugin key to not conflict with neotest.
Added a description for the keymap.
* fix(python): make both `ruff` and `ruff_lsp` available to user
Provide global variable to choose between `ruff` and `ruff_lsp` in
accordance to `pyright`/`basedpyright`
* refactor(python): ruff stuff
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
