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
Since I'm here bugging you, I was curious if you use any which key functionality such as provided by something like: https://github.com/folke/which-key.nvim
In looking at your repo docs I realized I am missing out on all this great lsp stuff you are providing. But when I try to explore it with which key I am seeing things like this:
where I can't see what each button actually does. It cuts off right before the relevant part. I'm thinking there is probably a way we can trim the repetitive first part and just show a description of the specific command to be called.
But is this something I should be tweaking with the which key plugin or is it something we have to provide through this coc-clojure plugin? I'll keep researching it myself and see if I can help but wanted to reach out in case you already have a better workflow that fixes this.
The text was updated successfully, but these errors were encountered:
Since I'm here bugging you, I was curious if you use any
which key
functionality such as provided by something like: https://github.com/folke/which-key.nvimIn looking at your repo docs I realized I am missing out on all this great lsp stuff you are providing. But when I try to explore it with
which key
I am seeing things like this:where I can't see what each button actually does. It cuts off right before the relevant part. I'm thinking there is probably a way we can trim the repetitive first part and just show a description of the specific command to be called.
But is this something I should be tweaking with the
which key
plugin or is it something we have to provide through thiscoc-clojure
plugin? I'll keep researching it myself and see if I can help but wanted to reach out in case you already have a better workflow that fixes this.The text was updated successfully, but these errors were encountered: