Disable flymake overlay click handler for code actions #731
Replies: 3 comments 1 reply
-
I have the same idea as you, but it seems that developers are not interested. |
Beta Was this translation helpful? Give feedback.
-
Unable to set, we have to use lsp-mode |
Beta Was this translation helpful? Give feedback.
-
I think it's much easier to disable it like this.
I'll accept a PR that decides which Flymake error classes to choose ( @lhjok I'm sorry I didn't reply to your issue but I didn't have much time and I couldn't make head or tails of it. I hope the above can help you. |
Beta Was this translation helpful? Give feedback.
-
I would like to be able to disable the click handler on code actions
I'm not sure how far you want to allow users to customize the properties applied to diagnostic types, so I wasn't able to come up with ready-to-review changes in a PR. Instead I tried a couple things locally until I was satisfied with the level of verbosity required in my configuration file in order to disable the click handler and mouse face, while still enabling other possible customization scenarios from other users eg. use right-click to trigger code action, apply a different face.
eglot.el
: https://github.com/joaotavora/eglot/blob/a697084/eglot.el#L1713-L1721dotemacs.el
I first considered a simple boolean defcustom to enable or disable the keymap and mouse-face specifically but I feel it wasn't customizable enough. I also wasn't able to determine whether it should warrant initializing
eglot-ignored-server-capabilities
with:codeActionProvider
.Btw, there is a small typo there:
Beta Was this translation helpful? Give feedback.
All reactions