Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jumping Highlights stay visible after jump #80

Open
Inch4Tk opened this issue Oct 2, 2021 · 0 comments
Open

Jumping Highlights stay visible after jump #80

Inch4Tk opened this issue Oct 2, 2021 · 0 comments

Comments

@Inch4Tk
Copy link

Inch4Tk commented Oct 2, 2021

When I use metaJump or metaSelect the created jumping highlights will stay until the editor tab is switched. See the attached gif:

jumpmarkers_dont_disappear

This started happening since I added an integrated terminal profile, with a custom path and setting it to the default terminal profile.

Like so:

"terminal.integrated.profiles.windows": {
        "Cmder": {
            "path": [
              "${env:windir}/Sysnative/cmd.exe",
              "${env:windir}/System32/cmd.exe"
            ],
            "args": ["/K",  "%cmder_root%/vendor/bin/vscode_init.cmd"]
        },
        "Testing": {
            "path": ["${env:windir}/System32/WindowsPowershell/v1.0/powershell.exe"]
        }
},
"terminal.integrated.defaultProfile.windows": "Cmder",

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):

"terminal.integrated.shell.windows": "${env:windir}/Sysnative/cmd.exe",
"terminal.integrated.shellArgs.windows": ["/K",  "%cmder_root%/vendor/bin/vscode_init.cmd"],

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?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant