zed
zed copied to clipboard
zed-industries
Setting to turn off lightning bolt
Check for existing issues
- [X] Completed
Is your feature request related to a problem?
I'm not keen on having lightning bolts everywhere in my code.
Describe the solution you'd like
A setting to turn off the lightning bolts on the start of lines.
If applicable, add mockups / screenshots to help present your vision of the feature
The lightning bolt is used to signify that a code action can be ran (cmd-. to trigger). Disabling the lightning bolt would mean the user wouldn't know if there is a code action available or not - is that something you'd be ok with? Would there be a better way to show that an action is available, or would you simply not care that you wouldn't know? Just curious to hear your opinions.
My workflow in my current editor (Neovim) is that I see a squiggly line under my code, and then I hit cmd+. to see the code actions. Isn't this flow pretty standard?
VS Code and JetBrains' IDEs both produce a lightbulb, near the gutter, when an action is available - I'm guessing that might've been the inspiration behind the lightning bolt in Zed. I personally don't use Vim mode or any Vim editor, so I'm not familiar with any behavior of those editors.
I see a squiggly line under my code, and then I hit cmd+. to see the code actions
In Zed, a squiggly line is already used to indicate an error or a warning, similar to VS Code or JetBrains IDEs. I would have thought that Neovim would use them that way too. The two concepts are related (because sometimes there are code actions for fixing an error), but not the same. Does the squiggly line actually indicate code actions in your Neovim setup?
Ok, it looks like they use a ‘>>’ instead of a lightning bolt?
Yes, but only on lines where code actions are available. In zed it's basically on every line. That's my issue here. I just think a setting to turn that off would be nice 🙂
VS Code and JetBrains' IDEs both produce a lightbulb, near the gutter, when an action is available
I hate that and got annoyed by the lightning bolt too. I think you should have a drawer where you list issues in the code and also quick actions.
To chime in, I personally don't use code actions in my workflow often -- only for expanding match arms. Otherwise I resort to a linter :) so I don't quite have a use for the lightning bolt, and don't mind disabling it if it was an option
+1 on this issue, most of the files in codebase have code action available ("organize imports") which I never want to do, but because code action is available, that bolt is following my cursor on each file on each line. I can be very distracting.
With the work that has been done on https://github.com/zed-industries/zed/pull/7665, perhaps adding a setting for lightning bolt removal would be easier?
On the flip side, I've been working with Zed for a while now and I dont even notice it popping up on each line in typescript codebases.
Turns out that pr did add it!
"gutter": {
"code_actions": false
}
I think the issue can be closed @albingroen
