-
Notifications
You must be signed in to change notification settings - Fork 26.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Return of "cannot find package bash-debug-adapter" #554
Comments
Thanks for the repott! Care to file a PR to fix this? |
Cheers @feoh , I've submitted a PR to restore that line. |
Thanks very much for the fix! Really appreciate the contribution! |
smrznuti1
pushed a commit
to smrznuti1/nvc
that referenced
this issue
Dec 17, 2024
smrznuti1
pushed a commit
to smrznuti1/nvc
that referenced
this issue
Dec 17, 2024
tomasgareau
added a commit
to tomasgareau/kickstart.nvim
that referenced
this issue
Jan 3, 2025
Addresses nvim-lua#1297 Currently, we're calling `require('mason').setup(...)` twice: * once when setting it as a dependency of `nvim-lspconfig` (since we set `config = true`) * once in the `config` function we define for `nvim-lspconfig` Calling setup twice can cause issues with, e.g., setting the `PATH` option: you might append Mason's bin dir in one setup call and prepend it in the other. We've kept the setup of `mason` in the `nvim-lspconfig` dependencies table since leaving it to the `config` function caused some plugin-loading-order related issues in the past. See: * nvim-lua#210 * nvim-lua#554 * nvim-lua#555 * nvim-lua#865
feoh
pushed a commit
that referenced
this issue
Jan 7, 2025
* fix: prevent mason setup from being run twice Addresses #1297 Currently, we're calling `require('mason').setup(...)` twice: * once when setting it as a dependency of `nvim-lspconfig` (since we set `config = true`) * once in the `config` function we define for `nvim-lspconfig` Calling setup twice can cause issues with, e.g., setting the `PATH` option: you might append Mason's bin dir in one setup call and prepend it in the other. We've kept the setup of `mason` in the `nvim-lspconfig` dependencies table since leaving it to the `config` function caused some plugin-loading-order related issues in the past. See: * #210 * #554 * #555 * #865 * docs: tweak comments per review feedback
dribic
pushed a commit
to dribic/nvim-files
that referenced
this issue
Jan 8, 2025
* fix: prevent mason setup from being run twice Addresses nvim-lua#1297 Currently, we're calling `require('mason').setup(...)` twice: * once when setting it as a dependency of `nvim-lspconfig` (since we set `config = true`) * once in the `config` function we define for `nvim-lspconfig` Calling setup twice can cause issues with, e.g., setting the `PATH` option: you might append Mason's bin dir in one setup call and prepend it in the other. We've kept the setup of `mason` in the `nvim-lspconfig` dependencies table since leaving it to the `config` function caused some plugin-loading-order related issues in the past. See: * nvim-lua#210 * nvim-lua#554 * nvim-lua#555 * nvim-lua#865 * docs: tweak comments per review feedback Signed-off-by: Dejan Ribič <[email protected]>
Mutex-
pushed a commit
to Mutex-/kickstart.nvim
that referenced
this issue
Jan 8, 2025
* fix: prevent mason setup from being run twice Addresses nvim-lua#1297 Currently, we're calling `require('mason').setup(...)` twice: * once when setting it as a dependency of `nvim-lspconfig` (since we set `config = true`) * once in the `config` function we define for `nvim-lspconfig` Calling setup twice can cause issues with, e.g., setting the `PATH` option: you might append Mason's bin dir in one setup call and prepend it in the other. We've kept the setup of `mason` in the `nvim-lspconfig` dependencies table since leaving it to the `config` function caused some plugin-loading-order related issues in the past. See: * nvim-lua#210 * nvim-lua#554 * nvim-lua#555 * nvim-lua#865 * docs: tweak comments per review feedback
ppizarro
pushed a commit
to ppizarro/my.vim
that referenced
this issue
Jan 8, 2025
* fix: prevent mason setup from being run twice Addresses nvim-lua/kickstart.nvim#1297 Currently, we're calling `require('mason').setup(...)` twice: * once when setting it as a dependency of `nvim-lspconfig` (since we set `config = true`) * once in the `config` function we define for `nvim-lspconfig` Calling setup twice can cause issues with, e.g., setting the `PATH` option: you might append Mason's bin dir in one setup call and prepend it in the other. We've kept the setup of `mason` in the `nvim-lspconfig` dependencies table since leaving it to the `config` function caused some plugin-loading-order related issues in the past. See: * nvim-lua/kickstart.nvim#210 * nvim-lua/kickstart.nvim#554 * nvim-lua/kickstart.nvim#555 * nvim-lua/kickstart.nvim#865 * docs: tweak comments per review feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I believe we have a regression of a bug fix 😅
The fix here: de1db70
Was removed recently: 6ffc5a1
To Reproduce
require 'kickstart.plugins.debug'
:MasonLog
Desktop
Neovim Version
The text was updated successfully, but these errors were encountered: