You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree. And probably we should have top level as well.
But let's ponder it all a bit...
Those args in the keybindings you link to intrigue me. If we create a tap command that takes arguments, and we make the same variables available to those arguments as we do with our current custom commands. Then we can bind keyboard shortcuts that tap anything we have defined variables for (and also code using the variables). We could then provide a few default shortcuts for obvious things like $current-form and $top-level-form. And the users can go crazy with it as well.
In fact we can take it a step further, I think... We can create a command that evaluates whatever args provided. And then provide default shortcuts with args like (tap> $current_form).
This ticket is for designing/approving a built-in tap current form
calva.tapCurrentForm
.Alt+Shift+Enter
seems to be free, I propose it as keybinding.Should we have tap top level form?
Related: https://github.com/seancorfield/vscode-clover-setup/blob/develop/keybindings.json
The text was updated successfully, but these errors were encountered: