| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix(command): run :MasonUpdate synchronously in headless mode (#1347) | William Boman | 2023-06-12 | 1 | -1/+0 |
| | | |||||
| * | chore: remove generate scripts and artifacts (#1246) | William Boman | 2023-04-22 | 1 | -12/+0 |
| | | |||||
| * | chore: consolidate generate task (#1171) | William Boman | 2023-04-02 | 1 | -4/+1 |
| | | |||||
| * | tests: add neotest dependency (#458) | William Boman | 2022-09-22 | 1 | -0/+1 |
| | | |||||
| * | feat: generate PACKAGES.md (#265) | William Boman | 2022-08-07 | 1 | -1/+5 |
| | | |||||
| * | refactor!: extract mason-lspconfig to separate plugin (#109) | William Boman | 2022-07-22 | 1 | -6/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 ↵ | William Boman | 2022-07-09 | 1 | -0/+15 |
| | | | | | checks (#36) | ||||
| * | mason.nvim | William Boman | 2022-07-07 | 1 | -1/+1 |
| | | |||||
| * | feat: integrate with lspconfig's on_setup hook (#631) | William Boman | 2022-04-27 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | | | | | | * 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 readme | ||||
| * | switch majority of installers to async implementation (#574) | William Boman | 2022-04-06 | 1 | -4/+4 |
| | | |||||
| * | add some tests (#360) | William Boman | 2021-12-25 | 1 | -0/+22 |
 |
index : mason | |
| [no description] | git mirrorbot |
| summaryrefslogtreecommitdiffstats |