Open Yarakashi-Kikohshi opened 2 years ago
I reproduced this. I have no idea to avoid this issue.
VS Code misunderstands that even extension.multiCommand.execute including args defines a keybinding for extension.multiCommand.execute alone.
I think so too.
There are two simple solutions.
Divide extension.multiCommand.execute
into two commands.
Currently, the command has two features:
args
. (in keybindings.json)Of course, when divide the command into two, user may be confused.
Accept this problem and do not mind if you see keybinding like that in command palette. If so, you need to write a note in README.
Incorrect keybindings appear in command palette when manual execution
I haven't defined such a keybinding. The command actually executed by the keybinding displayed here is sequence defined in multi-command.
To reproduce
To avoid the problem raised in # 16, the keybinding is defined as follows:
Keybindings for
extension.multiCommand.execute
are not defined.To avoid this problem
This problem does not occur if you define the keybindings as follows:
However, there are # 16 potential issues with this solution.
Alternatively, to really define keybinding for
extension.multiCommand.execute
. However, I don't want to define a keybinding because I think it's enough to call it from command palette.Possible causes
VS Code misunderstands that even
extension.multiCommand.execute
includingargs
defines a keybinding forextension.multiCommand.execute
alone.