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
I don't have any of the environment variables, but opening a shell script logs the following warning to ~/.local/state/nvim/lsp.log when the LSP server attaches to a buffer.
[WARN][2024-11-18 21:19:33] ...lsp/handlers.lua:625 "05:19:33.609 WARNING ⛔️ Environment variable configuration is being deprecated, please use workspace configuration. The following environment variables were used: shfmt"
How often does it reproduce? Is there a required condition?
It reproduces when the LSP server attaches to a buffer for the first time in the session. Closing neovim and reopening the file will add another warning to the log file.
What is the expected behavior?
I expect that the code correctly determines whether any of the config environment variables are being used.
What do you see instead?
This might be the place the warning is talking about, because the shfmt key is an object.
Code editor
nvim
Platform
Linux (Ubuntu)
Version
5.4.2
What steps will reproduce the bug?
I don't have any of the environment variables, but opening a shell script logs the following warning to
~/.local/state/nvim/lsp.log
when the LSP server attaches to a buffer.How often does it reproduce? Is there a required condition?
It reproduces when the LSP server attaches to a buffer for the first time in the session. Closing neovim and reopening the file will add another warning to the log file.
What is the expected behavior?
I expect that the code correctly determines whether any of the config environment variables are being used.
What do you see instead?
This might be the place the warning is talking about, because the
shfmt
key is an object.bash-language-server/server/src/config.ts
Lines 104 to 107 in 1ebe533
Additional information
No response
The text was updated successfully, but these errors were encountered: