New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
The suggestions provided by which-key do not describe what the key does #7882
Comments
After doing some debugging on Gitter, found out that this is caused by a new which-key update. Rolling back to an older slot will fix this. |
That indeed solved the issue! Thanks! Is it helpful to leave this issue open, or do you prefer I close it out? I'm not sure if something in spacemacs needs to be changed, or if perhaps the latest which-key contains a bug. |
I think we should leave the issue open. Its a workaround to downgrade and not an actual fix. |
May be justbur/emacs-which-key#155 Seems it has been fixed upstream and waiting for melpa to rebuild |
Fixed |
Thanks! I just updated and it did indeed work as expected. The issue appears to have been resolved. |
Description
The entries provided by which-key seem to be wrong. It appears that something like a namespace is rendered rather than a helpful function name.
Reproduction guide 馃
SPC r r
(The same issues seems to apply to all which-key suggestions, I just happened to choose
SPC r r
.)Observed behaviour: 馃憖 馃挃
The suggestions provided by which-key are all the same:
ruby/RuboCop
.Expected behaviour: 鉂わ笍 馃槃
The suggestions provided by which-key give an accurate description of what is going to happen, e.g.
rubocop-check-current-file
,rubocop-check-project
, etc.System Info 馃捇
The text was updated successfully, but these errors were encountered: