Closed stevenguh closed 2 years ago
Sure, I will try to test this today
I followed the contributing guide on how to do the first setup.
Then I used this usually by typing spc
. I am testing the right thing or am I just testing normal VSpaceCode?
By the way:
mx
test in linux).Doubts: how do I test this?
Tested desc bind menu (C-h) Tested hide option via overrides
Then I used this usually by typing spc. I am testing the right thing or am I just testing normal VSpaceCode?
That should work, and should be using the new which key core.
Tested desc bind menu (C-h)
Press Control-h
in any which key menu to launch the "Search binding" menu.
Tested hide option via overrides
Try adding a binding with "display": "hidden"
in the override. That item will not be shown but can still be trigger by key.
For example: The blame shouldn't be shown in the UI of the <spc> g
menu, but should still works with b
key.
"vspacecode.bindingOverrides": [
{
"keys": "g.b",
"name": "Blame",
"type": "command",
"display": "hidden",
"command": "gitlens.toggleFileBlame"
},
]
Both works fine for me!
Thanks Marco :)
Fix #38, #51.
This pull request contains a rewrite of the core of which-key to
Tests performed:
Manual tests
Race condition
sleep 1; xdotool type " "; sleep 0.001; xdotool type "mx"
Other smoke tests
@MarcoIeni Just wondering if you have some time to try it out and make sure I am not breaking anything major?