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

Can't change back to default cursor shape after enter and exit out of neovim. #5904

Closed
ianyepan opened this issue May 14, 2020 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ianyepan
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.778]
Windows Terminal version (if applicable): 0.11.1251.0

Any other software? neovim, WSL1

Short bug description

Windows Terminal fails to change back to default cursor shape after I enter and exit out of neovim.

Steps to reproduce

  1. Set the cursor shape in Windows Terminal to be "vintage" (i.e. thick underscore) in settings.json.
  2. Open a terminal session in WSL1 (Ubuntu 18.04).
  3. Invoke neovim on a random file with nvim main.cpp.
  4. Exit neovim with :q<enter>

Expected behavior

  1. Invoke neovim at the command line, the cursor shape is vintage before entering the neovim session. So far so good.
  2. Entered neovim, the cursor shape is now filled-box in "neovim's normal-mode", and is a vertical thin line in "neovim's insert-mode". So far so good.
  3. After I exit out of neovim, Windows Terminal should give me back the vintage cursor shape at the command line, which I specified as the default in settings.json.

Actual behavior

Windows Terminal fails to change back to default cursor shape after I enter and exit out of neovim. The cursor now becomes filled-box shape (as in neovim's normal mode).

@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 May 14, 2020
@zadjii-msft
Copy link
Member

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1604 for more discussion.

/dup #1604

@ghost
Copy link

ghost commented May 14, 2020

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 May 14, 2020
@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 May 14, 2020
@ianyepan
Copy link
Author

@zadjii-msft Hey Mike, thanks for the pointer. I'll follow that thread instead :-)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants