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 could not figure out why but since recently formatting does not seem to work anymore.
When I try to manually invoke !alejandra % it works (and I have set alejandra as the formatting command as well), but using my shortcut (or invoking vim.lsp.buf.format()) does not format anything but also does not give any errors.
Neither as an instant message nor in LspLog.
The server is running, I get code-completion.
I also tried formatting in lua files which does work.
My neovim version is: v0.10.0-dev-4e59422
My nil version is the latest on nixpkgs-unstable: 2023-08-09 (I saw that there were a few commits since then so I'll try to test it with a newer version as soon as I find the time for that. It's not really a problem for now though)
The text was updated successfully, but these errors were encountered:
I cannot reproduce the issue on current master and alejandra works fine with LSP formatting command.
!alejandra %
alejandra will modify the file directly by themselves, while our configuration expects a command that processes source from stdin and print into stdout. So you are expected to use command alejandra -- in the configuration, like this:
I could not figure out why but since recently formatting does not seem to work anymore.
When I try to manually invoke
!alejandra %
it works (and I have set alejandra as the formatting command as well), but using my shortcut (or invokingvim.lsp.buf.format()
) does not format anything but also does not give any errors.Neither as an instant message nor in LspLog.
The server is running, I get code-completion.
I also tried formatting in lua files which does work.
My neovim version is:
v0.10.0-dev-4e59422
My nil version is the latest on nixpkgs-unstable:
2023-08-09
(I saw that there were a few commits since then so I'll try to test it with a newer version as soon as I find the time for that. It's not really a problem for now though)The text was updated successfully, but these errors were encountered: