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.

Sign up for GitHub

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

Jump to bottom

Bug Report running vim changes cursor style #2793

Closed
nree opened this issue Sep 17, 2019 · 2 comments
Closed

Bug Report running vim changes cursor style #2793

nree opened this issue Sep 17, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@nree
Copy link

nree commented Sep 17, 2019

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.356]
Windows Terminal version (if applicable):  Windows Terminal Preview v0.4.2382.0

Any other software?
wsl 1 , ubuntu disco, neovim 0.3.8

Steps to reproduce

  1. Change cursor to 'vintage' for default Ubuntu profile
  2. $ vim -> :q after
  3. cursor is no longer vintage, now it's filledBox

Expected behavior

My cursor to return to vintage

Actual behavior

My cursor does not return to vintage but instead keeps the cursor from vim / neovim
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 17, 2019
@DHowett-MSFT
Copy link
Contributor

/dup #1604

@ghost
Copy link

ghost commented Sep 17, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Sep 17, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 17, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nree @DHowett-MSFT