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
When setting a native integrated default profile like "terminal.integrated.defaultProfile.windows": "PowerShell" the issue does not happen. At first I thought it could be a cmder issue, but directly referencing PowerShell via a custom profile with a path will also reproduce the issue.
Overriding the terminal profile by setting the deprecated `"terminal.integrated.shell.windows" will fix the issue (even when the other setting is still in the settings file):
I am honestly not 100% sure if this is a metaGo issue, but I could not reproduce this behavior with any of the default vscode movement/select actions. I would debug it further myself, but the source code for all submodules is currently set to private (intended or just an oversight?).
The text was updated successfully, but these errors were encountered:
When I use metaJump or metaSelect the created jumping highlights will stay until the editor tab is switched. See the attached gif:
This started happening since I added an integrated terminal profile, with a custom path and setting it to the default terminal profile.
Like so:
When setting a native integrated default profile like
"terminal.integrated.defaultProfile.windows": "PowerShell"
the issue does not happen. At first I thought it could be a cmder issue, but directly referencing PowerShell via a custom profile with a path will also reproduce the issue.Overriding the terminal profile by setting the deprecated `"terminal.integrated.shell.windows" will fix the issue (even when the other setting is still in the settings file):
I am honestly not 100% sure if this is a metaGo issue, but I could not reproduce this behavior with any of the default vscode movement/select actions. I would debug it further myself, but the source code for all submodules is currently set to private (intended or just an oversight?).
The text was updated successfully, but these errors were encountered: