mason/Makefile, branch feat/socket-integration[no description]http://git.sudomsg.com/mirror/mason/atom/Makefile?h=feat%2Fsocket-integration2023-06-12T23:16:55Zfix(command): run :MasonUpdate synchronously in headless mode (#1347)2023-06-12T23:16:55ZWilliam Bomanwilliam@redwill.se2023-06-12T23:16:55Zurn:sha1:02767937fc2e1b214c854a8fdde26ae1d3529dd6chore: remove generate scripts and artifacts (#1246)2023-04-22T10:22:54ZWilliam Bomanwilliam@redwill.se2023-04-22T10:22:54Zurn:sha1:e239c6439cad2f4c9bd247775815e0be3741621cchore: consolidate generate task (#1171)2023-04-02T19:38:20ZWilliam Bomanwilliam@redwill.se2023-04-02T19:38:20Zurn:sha1:bd5f5924e99eb20effc3199710ab754e89f7a7b3tests: add neotest dependency (#458)2022-09-22T23:14:17ZWilliam Bomanwilliam@redwill.se2022-09-22T23:14:17Zurn:sha1:da731a77dd134e702a3d3ae0655305bcf9b2d023feat: generate PACKAGES.md (#265)2022-08-07T16:31:20ZWilliam Bomanwilliam@redwill.se2022-08-07T16:31:20Zurn:sha1:d1c860da4b89fd29a45decfb490c79748d954493refactor!: 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"
```chore(workflow): modularize scripts and remove mason-lspconfig from CI checks (#36)2022-07-08T23:00:34ZWilliam Bomanwilliam@redwill.se2022-07-08T23:00:34Zurn:sha1:d132a7a673d43b2da73f75e09fbe7fb49c431514mason.nvim2022-07-06T22:39:59ZWilliam Bomanwilliam@redwill.se2022-07-06T17:41:43Zurn:sha1:5f634e0c37e723fc0c33e06b4fd5c2180178db40feat: integrate with lspconfig's on_setup hook (#631)2022-04-27T19:20:45ZWilliam Bomanwilliam@redwill.se2022-04-27T19:20:45Zurn:sha1:090c8a87b31de5c5a21eebc55adb22ddab625015
* feat: integrate with lspconfig's on_setup hook
* fix!: don't use aliased installation directories if new .setup() fn is used
This makes it so servers are always installed in a directory name that
corresponds with the server name. The reason aliased installation directories
is supported is lost on me, but it's legacy and complicates things
unnecessarily.
This is a breaking change for users who previously were using the `.on_server_ready()`
hook, and now transitioned to setting up servers directly via lspconfig.
These users will need to reinstall the server.
* fix: block usage of the deprecated server:setup() method if new setup method is used
* fix: allow passing no arg to setup()
* docs: ok final.v3 readmeswitch majority of installers to async implementation (#574)2022-04-05T22:25:50ZWilliam Bomanwilliam@redwill.se2022-04-05T22:25:50Zurn:sha1:999476c324b26223aaf409a84497215e18d74499add some tests (#360)2021-12-25T14:11:42ZWilliam Bomanwilliam@redwill.se2021-12-25T14:11:42Zurn:sha1:d7e233566543d4c83199f5644f90bb116d7070f2