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
There are two code actions provided by ruff-lsp that are always shown:
Ruff: Organize Imports
Ruff: Fix All
Both of them do nothing when they are selected.
Note that when I select the I rule I have another code action that pops which is Ruff (I001): Organize imports which does work. It's the two code actions that are always shown that do nothing.
Reproduction Steps
I am building helix from source on the master branch (updated on the 27th of september 2023).
Note that in my config I have both pylsp and ruff-lsp activated, but I tried running only ruff-lsp and it did not help.
I open the code actions menu (<space-a>) and select the organize imports or the fix all code action
Nothing happens
I opened an issue on the ruff-lsp repo and I tried the config kindly provided by Charlie Marsch on the latest stable release. On this release, both code actions work, but on the master branch I cannot get them to work.
Summary
There are two code actions provided by ruff-lsp that are always shown:
Ruff: Organize Imports
Ruff: Fix All
Both of them do nothing when they are selected.
Note that when I select the
I
rule I have another code action that pops which isRuff (I001): Organize imports
which does work. It's the two code actions that are always shown that do nothing.Reproduction Steps
Python lsp config
<space-a>
) and select the organize imports or the fix all code actionI opened an issue on the ruff-lsp repo and I tried the config kindly provided by Charlie Marsch on the latest stable release. On this release, both code actions work, but on the master branch I cannot get them to work.
Helix log
~/.cache/helix/helix.log (master branch)
~/.cache/helix/helix.log (latest stable release)
Platform
Linux
Terminal Emulator
kitty 0.29.2
Helix Version
helix 23.05-450-gba063714
The text was updated successfully, but these errors were encountered: