Prefix key hint duration setting?
已回答
I use prefix key bindings a lot to group related functions to a single primary key with a second function specifier.
One issue with this is that the second key hint remains on screen for about 1 second.
How do I increase that duration?
Alternately, what's the downside to leaving that "second key options" help text on screen until the 2nd key, or ESC is pressed?
请先登录再写评论。
May you show the screenshot of the popup that disappears after a second? Could be related to tooltip delay:
Konstantin Annikov, yes, thanks that did allow me to prolong the presence of these hints, but doesn't that also now delay the time before tooltips show up?
I take it back, no effect.
I had chosen 2 sec as a test, but that seems to be the default. So, seemed like it was working for that value.
Setting to 5000 still clears the into after ~2 seconds.
May you show the screenshot of the popup you are talking about?
I have Ctrl-w bound as a window action prefix, with several 2nd key commands (bit like the vim bindings) :
A = close all
C = close
O = close others
V = vert split
H = horix split
You can see this in the red box I added below.
These remain on screen for about 2 seconds.
The message is then overwritten with "Auto fetch: finished (XX minutes ago)", where XX is some numeric, ever increasing value.
Perhaps the issue is the "auto fetch" should not be continuously updating the status line?
I disabled the the VCS background auto-refresh and now the "Prefix key pressed...." message is simply cleared. The area is blank afterwards.
Oh, this message is generated by the Vim plugin.
Please file an issue at https://youtrack.jetbrains.com/issues/VIM
I'm not using the vim plugin. I had it disabled earlier, but have now uninstalled to confirm no interference.
Same issue, the "Prefix key pressed ... <list of second key options>" still appears, and is still overwritten by some other status message later.
Today it's this message that's doing the overwriting.
I have to ask, why should a status update that happened minutes ago continue to report how long ago it happened with an ever increasing time value and overwrite a mid-command prompt?
This is a bug. Here is the link: https://youtrack.jetbrains.com/issue/IDEA-152762
Feel free to upvote and comment inside.
Yep, definitely the same problem. Thanks for pointing it out.