You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is really annoying sometimes when the cwd functions to attach lsps to current buffer dont work because sometimes a ppl are not on a framework and not on git (sometimes) and then they wonder why the lsp wont attach,
for eg if i do some php scripting , just core php then there is no lsp attached if i dont initialize git, ik it is stupid to do projects without git but still the lsp should be able to attach to current file via some kinda method or so, it would be really helpful if this feature gets added to nvim-lspconfig , Thanks.
The text was updated successfully, but these errors were encountered:
Thanks for your report. The configs in this repo are unsupported and provided only as a starting point. We depend on users (like you) to troubleshoot issues with their specific LSP setups and send improvements.
If you found a bug in the core Nvim vim.lsp module (not part of this repo), the best way to get it fixed is to report to Nvim (not nvim-lspconfig) with:
steps to reproduce it without the particular LSP server and other factors particular to your environment
(optional, but very helpful): by adding a failing test case to lsp_spec.lua, which has code to setup a fake LSP server to simulate various scenarios
Description
it is really annoying sometimes when the cwd functions to attach lsps to current buffer dont work because sometimes a ppl are not on a framework and not on git (sometimes) and then they wonder why the lsp wont attach,
for eg if i do some php scripting , just core php then there is no lsp attached if i dont initialize git, ik it is stupid to do projects without git but still the lsp should be able to attach to current file via some kinda method or so, it would be really helpful if this feature gets added to nvim-lspconfig , Thanks.
The text was updated successfully, but these errors were encountered: