Holding the ctrl key down the whole time. Not only would the feature be convenient and allow for better host OS GUI integration, but VSCode would be more CPU-efficient for common usages. When using vscode-go, this means significant extraneous energy usage which could be avoided almost entirely by providing modifier key settings for "peek definition".
This means calls to godef are happening when the user is pressing a very common key with no intention of obtaining contextual hover information.
copy, paste, opening the command palette, etc.). As I describe in microsoft/vscode-go#257 (comment):įor example, with the cursor resting still in the editor area, pressing ⌘ instantly invokes the GoDefinitionProvider, even when ⌘ is immediately used in a chord for some other command (e.g. If a plugin must do some work to provide the definition, it's very likely VSCode will ask plugins for definition information even when the user has no intention of obtaining it. Consider the hard-coded modifier associated with the "peek definition" functionality. I've found an interesting performance implication resulting from the current defaults/lack of configurability.
0 kommentar(er)
