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
Preventing wrap from invoking wrap itself directly was an easy fix.
New problem
But I noticed another possibility of deadlock. That is an indirect recursive invocation of wrap.
Possible solution
Calling wrap from any way other than keystrokes is always wrong. The wrap command is intended to be invoked only from user keystrokes directly.
Making wrap command not return Promise could be a solution.
This keybinding triggers a deadlock, and vscode would become unresponsive for most of the keyboard shortcuts.
This example doesn't make any sense but even it shouldn't break vscode.
The text was updated successfully, but these errors were encountered: