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

cursor can't restore its shape after leaving Vim and WSL #17846

New Issue
Closed
opened 2026-01-31 05:56:08 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 05:56:08 +00:00
Owner
Copy Link

Originally created by @thezbm on GitHub (Jul 2, 2022).

Windows Terminal version

1.13.11432.0

Windows build number

10.0.22000.0

Other Software

Ubuntu 22.04 LTS
Neovim v0.7.0

Steps to reproduce

The cursor is currently a blinking bar as I set in the configuration for WT.
Then enter Ubuntu by entering wsl.
Open nvim.
Quit it.
Quit WSL.

https://user-images.githubusercontent.com/24851999/177004315-ef88ec13-1651-4872-ad1b-13844f4fa14b.mp4

Expected Behavior

The cursor should be stored to a blinking bar immediately after I quit Neovim.

Actual Behavior

The cursor continues to be a white block.
It seems that after Neovim changed the shape of the text input cursor, Windows Terminal didn't change it back.

Originally created by @thezbm on GitHub (Jul 2, 2022). ### Windows Terminal version 1.13.11432.0 ### Windows build number 10.0.22000.0 ### Other Software Ubuntu 22.04 LTS Neovim v0.7.0 ### Steps to reproduce The cursor is currently a blinking bar as I set in the configuration for WT. Then enter Ubuntu by entering `wsl`. Open `nvim`. Quit it. Quit WSL. https://user-images.githubusercontent.com/24851999/177004315-ef88ec13-1651-4872-ad1b-13844f4fa14b.mp4 ### Expected Behavior The cursor should be stored to a blinking bar immediately after I quit Neovim. ### Actual Behavior The cursor continues to be a white block. It seems that after Neovim changed the shape of the text input cursor, Windows Terminal didn't change it back.
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:56:08 +00:00
claunia commented 2026-01-31 05:56:10 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jul 2, 2022):

I'm afraid this is known issue with neovim (see https://github.com/neovim/neovim/issues/4396), and their recommended workaround is to reset the cursor manually with a VimLeave handler.

See also #9081.

@j4james commented on GitHub (Jul 2, 2022): I'm afraid this is known issue with neovim (see https://github.com/neovim/neovim/issues/4396), and their recommended workaround is to reset the cursor manually with a `VimLeave` handler. See also #9081.
claunia commented 2026-01-31 05:56:10 +00:00
Author
Owner
Copy Link

@thezbm commented on GitHub (Jul 2, 2022):

I'm afraid this is known issue with neovim (see neovim/neovim#4396), and their recommended workaround is to reset the cursor manually with a VimLeave handler.

See also #9081.

Oh, I see. Thanks for your time. I managed to fix it with a VimLeave autocmd.
See #4867 for more information.

@thezbm commented on GitHub (Jul 2, 2022): > I'm afraid this is known issue with neovim (see [neovim/neovim#4396](https://github.com/neovim/neovim/issues/4396)), and their recommended workaround is to reset the cursor manually with a `VimLeave` handler. > > See also #9081. Oh, I see. Thanks for your time. I managed to fix it with a `VimLeave` autocmd. See [#4867](https://github.com/neovim/neovim/issues/4867) for more information.
claunia commented 2026-01-31 05:56:10 +00:00
Author
Owner
Copy Link

@awa5114 commented on GitHub (Mar 23, 2023):

@j4james what if I'm using neovim?

@awa5114 commented on GitHub (Mar 23, 2023): @j4james what if I'm using neovim?
claunia commented 2026-01-31 05:56:10 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 23, 2023):

@j4james what if I'm using neovim?

@amine-aboufirass I don't understand what you're asking. The issue I linked above, and the suggested workaround is for neovim.

@j4james commented on GitHub (Mar 23, 2023): > @j4james what if I'm using neovim? @amine-aboufirass I don't understand what you're asking. The issue I linked above, and the suggested workaround _is_ for neovim.
claunia commented 2026-01-31 05:56:11 +00:00
Author
Owner
Copy Link

@awa5114 commented on GitHub (Apr 9, 2023):

@j4james I see, I misread your comment.

I have tried opening an nvim instance on Windows Terminal (no WSL) and then doing :au VimLeave * set guicursor=a:block-blinkon0. When I :q! out of nvim I unfortunately see the same behavior and the cursor doesn't change back.

@awa5114 commented on GitHub (Apr 9, 2023): @j4james I see, I misread your comment. I have tried opening an `nvim` instance on Windows Terminal (no WSL) and then doing `:au VimLeave * set guicursor=a:block-blinkon0`. When I `:q!` out of `nvim` I unfortunately see the same behavior and the cursor doesn't change back.
claunia commented 2026-01-31 05:56:11 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 9, 2023):

I have tried opening an nvim instance on Windows Terminal (no WSL) and then doing :au VimLeave * set guicursor=a:block-blinkon0.

Note that what you're requesting there is a block cursor that doesn't blink. If that's not the style you want it changed back to, it's obviously not going to work. For example, if you want to change it back to a horizontal bar that does blink, you'd need to do something like this:

:au VimLeave * set guicursor=a:hor1-blinkon1

If you don't want to have to specify the exact cursor type, and just want it changed back to whatever you've configured in the Windows Terminal settings, I don't know of an easy way to do that, but one of the suggestions in the nvim issue tracker was this:

:au VimLeave * set guicursor= | call chansend(v:stderr, "\x1b[ q")

That said, if you're not using the WSL version of nvim, I'm not which of these options will work, if any.

@j4james commented on GitHub (Apr 9, 2023): > I have tried opening an `nvim` instance on Windows Terminal (no WSL) and then doing `:au VimLeave * set guicursor=a:block-blinkon0`. Note that what you're requesting there is a block cursor that doesn't blink. If that's not the style you want it changed back to, it's obviously not going to work. For example, if you want to change it back to a horizontal bar that _does_ blink, you'd need to do something like this: :au VimLeave * set guicursor=a:hor1-blinkon1 If you don't want to have to specify the exact cursor type, and just want it changed back to whatever you've configured in the Windows Terminal settings, I don't know of an easy way to do that, but one of the suggestions in the nvim issue tracker was this: :au VimLeave * set guicursor= | call chansend(v:stderr, "\x1b[ q") That said, if you're not using the WSL version of nvim, I'm not which of these options will work, if any.
claunia commented 2026-01-31 05:56:11 +00:00
Author
Owner
Copy Link

@BoscoDomingo commented on GitHub (Jan 16, 2025):

For reference to anyone googling this issue: I fixed it by setting my cursor to be a line (same as I use in my Windows Terminal). No need for an autocmd. In my init.lua:

vim.opt.guicursor = "a:ver30-Cursor-blinkwait700-blinkon400-blinkoff250"

Reference

@BoscoDomingo commented on GitHub (Jan 16, 2025): For reference to anyone googling this issue: I fixed it by setting my cursor to be a line (same as I use in my Windows Terminal). No need for an autocmd. In my `init.lua`: ``` vim.opt.guicursor = "a:ver30-Cursor-blinkwait700-blinkon400-blinkoff250" ``` [Reference](https://vimhelp.org/options.txt.html#%27guicursor%27)
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 Issue-Bug Needs-Tag-Fix Needs-Triage
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#17846
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?