* fix(ui): do not add trouble to lualine when aerial is enabled
* refactor: make trouble lualine an option
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
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.
`LazyVim.config` gets evaluated during the parsing phase with `opts`
as a table (thus not taking into account changes made in the user's
personal configuration for the icons), so make `opts` a function to
defer the evaluation until the plugin loads.
