starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 01:21:51 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:21:51 +00:00
Owner
Copy Link

Originally created by @ianyepan on GitHub (May 14, 2020).

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

Originally created by @ianyepan on GitHub (May 14, 2020). # Environment ```none 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 0. Set the cursor shape in Windows Terminal to be "vintage" (i.e. thick underscore) in `settings.json`. 1. Open a terminal session in WSL1 (Ubuntu 18.04). 2. Invoke neovim on a random file with `nvim main.cpp`. 3. 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`. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # 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).
claunia added the Resolution-Duplicate label 2026-01-31 01:21:51 +00:00
claunia commented 2026-01-31 01:21:52 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 14, 2020):

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

@zadjii-msft commented on GitHub (May 14, 2020): 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
claunia commented 2026-01-31 01:21:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (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 commented on GitHub (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!
claunia commented 2026-01-31 01:21:52 +00:00
Author
Owner
Copy Link

@ianyepan commented on GitHub (May 14, 2020):

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

@ianyepan commented on GitHub (May 14, 2020): @zadjii-msft Hey Mike, thanks for the pointer. I'll follow that thread instead :-)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8141
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?