mason/scripts/lua/mason-scripts/mason-lspconfig, branch main[no description]http://git.sudomsg.com/mirror/mason/atom/scripts/lua/mason-scripts/mason-lspconfig?h=main2022-07-22T01:15:43Zrefactor!: extract mason-lspconfig to separate plugin (#109)2022-07-22T01:15:43ZWilliam Bomanwilliam@redwill.se2022-07-22T01:15:43Zurn:sha1:11c0af44e69a165df41e5fe6681b47f4204d3623
The rationale behind this is to make boundaries clearer as mason.nvim
has no direct relation with lspconfig per se.
Also, hopefully, by having it as a separate package like this would
encourage more people to write similar extensions (think mason-dap and
mason-null-ls). Ideally such extensions wouldn't be required at all, but
there are definitely gaps to fill as of today.
From now on you'll need to add `williamboman/mason-lspconfig.nvim` as
a plugin if you want to use the `mason-lspconfig` extension:
```lua
use {
{ "williamboman/mason.nvim", branch = "alpha" },
"williamboman/mason-lspconfig.nvim",
"neovim/nvim-lspconfig",
}
```
```lua
Plug "williamboman/mason.nvim", { 'branch': 'alpha' }
Plug "williamboman/mason-lspconfig.nvim"
Plug "neovim/nvim-lspconfig"
```fix(mason-lspconfig): patch some server's cmd on Windows (#100)2022-07-19T22:00:55ZWilliam Bomanwilliam@redwill.se2022-07-19T22:00:55Zurn:sha1:619e52abec0175620a6b8af4e18ed4cfb4857825chore(workflow): modularize scripts and remove mason-lspconfig from CI checks (#36)2022-07-08T23:00:34ZWilliam Bomanwilliam@redwill.se2022-07-08T23:00:34Zurn:sha1:d132a7a673d43b2da73f75e09fbe7fb49c431514