### Description
I am the author of this
[PR](https://github.com/LazyVim/LazyVim/pull/2890).
While reviewing my own code and checking the LazyVim official website, I
noticed some inconsistencies 😓 , so I created a small PR to address
them:
### Changes
1.Each optional plugin has a comment message indicating that the plugin
is optional, but DAP does not (as shown in the image). Since the
official website already has an "optional" in title.
**I removed the comment messages regarding "optional" to avoid
confusion**.
<img width="300" alt="Screenshot 2024-05-23 at 10 31 38 PM"
src="441979fc-20dd-4599-a91d-f27bc0841d79">
---
2. I changed the DAP to use local variables for DAP to maintain
consistency, even though both require statements reference the same
module.
## Problem
Treesitter was not working in angular html templates after enabling
`lang.angular` extra.
## Solution
Added a change recommeded by angular treesitter developer to enable
treesitter for components and containers.
### Reference to recommendation in treesitter docs
[Reference to the recommendation for this
hack](https://github.com/dlvandenberg/tree-sitter-angular?tab=readme-ov-file#filetype).
In the future we can add:
- dap / debugger support, if this is ever possible or needed.
- extend neotest, if this is ever needed, for most people I suspect not
needed.
- linting, if this is ever needed.
- ~~maybe enhance nvim-cmp behavior with nixpkgs, rust lang extension
crates.nvim does smt with nvim-cmp, other language extensions don't.~~
I think its already good to merge this PR, we can add these enhancements
later, if they are ever needed.
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
## Description
This will add minimal support for [Nushell](https://www.nushell.sh/)
include lspconfig and treesitter highlight
## Additional Context
Close#2164
---------
Co-authored-by: Folke Lemaitre <folke.lemaitre@gmail.com>
* feat(extras): Add extra for angular lspconfig
Since treesitter has better support for angular parser recently that works for the legacy and the latest version of it,
I am happy to suggest this extra configuration that works for well for me without any issue.
And since lack of references about how to config the angular lsp inside of neovim out there, this will work fine as a starting point.
* feat(extras): Added `angularls` lsp configuration
* feat(extras.lang): update `angularls` configuration
---------
Co-authored-by: Radvil <radvil.linux@gmail.com>
* 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.
