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

WT stops cursor blinking after quitting Emacs nox build #16644

New Issue
Closed
opened 2026-01-31 05:18:19 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 05:18:19 +00:00
Owner
Copy Link

Originally created by @angelog0 on GitHub (Feb 4, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.1503

Other Software

emacs nox build from master in WSL2
emacs msys2 package (for terminals)

Steps to reproduce

  • Start WT-WSL2: cursor is blinking
  • Start Emacs: cursor is blinking
  • Quit Emas: at WSL prompt the cursor is no longer blinking.

The same occurs running, in WT, Emacs from MSYS2 package.

NOTICE that THE SAME STEPS in MinTTY terminal (with or without WSL) produce a BLINKING cursor after quitting Emacs!.

I see there are similar issue flagged here but in my case the cursor stops blinking ONLY after QUITTING Emacs, not running a curser app...

Originally created by @angelog0 on GitHub (Feb 4, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.1503 ### Other Software emacs nox build from master in WSL2 emacs msys2 package (for terminals) ### Steps to reproduce - Start WT-WSL2: cursor is blinking - Start Emacs: cursor is blinking - Quit Emas: at WSL prompt the cursor is no longer blinking. The same occurs running, in WT, Emacs from MSYS2 package. NOTICE that THE SAME STEPS in MinTTY terminal (with or without WSL) produce a BLINKING cursor **after quitting Emacs**!. I see there are similar issue flagged here but in my case the cursor stops blinking ONLY after QUITTING Emacs, not running a curser app...
claunia added the Resolution-Duplicate label 2026-01-31 05:18:19 +00:00
claunia commented 2026-01-31 05:18:20 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 6, 2022):

I'm almost sure this is the same thing as #10754, and Emacs is probably using cnorm/cursor_normal on exit, which disables the cursor blinking mode.

I'm not sure why you're getting different results in Mintty, unless you've configured your TERM variable to something weird. If you execute tput cnorm in Mintty, does that disable blinking?

@j4james commented on GitHub (Feb 6, 2022): I'm almost sure this is the same thing as #10754, and Emacs is probably using cnorm/cursor_normal on exit, which disables the cursor blinking mode. I'm not sure why you're getting different results in Mintty, unless you've configured your `TERM` variable to something weird. If you execute `tput cnorm` in Mintty, does that disable blinking?
claunia commented 2026-01-31 05:18:20 +00:00
Author
Owner
Copy Link

@angelog0 commented on GitHub (Feb 8, 2022):

@j4james, I did not change TERM in MinTTY. It still is

$ echo $TERM
xterm

BTW, after I quit Emacs (and cursor stops blinking), restarting Emacs the cursor returns to blinking in Emacs; exiting one more time, it returns to stop blinking...

@angelog0 commented on GitHub (Feb 8, 2022): @j4james, I did not change TERM in MinTTY. It still is ``` $ echo $TERM xterm ``` BTW, after I quit Emacs (and cursor stops blinking), restarting Emacs the cursor returns to blinking **in Emacs**; exiting one more time, it returns to stop blinking...
claunia commented 2026-01-31 05:18:20 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 8, 2022):

I think I know what's happening now. It looks like Mintty ignores the blinking escape sequence (private mode 12) if you've set your default cursor preference to be blinking, so that's why it appears to be working. Emacs is still requesting that the cursor stop blinking, but Mintty is simply ignoring that request.

BTW, after I quit Emacs (and cursor stops blinking), restarting Emacs the cursor returns to blinking in Emacs; exiting one more time, it returns to stop blinking...

That is exactly what I would expect. They're likely using the cvvis terminfo capability on startup (which enables cursor blinking), and the cnorm capability on shutdown (which disables blinking).

The bottom line is that this is a duplicate of #10754 and is really an Emacs problem. You can probably work around it by editing your terminfo if you don't ever want applications to stop your cursor blinking.

@j4james commented on GitHub (Feb 8, 2022): I think I know what's happening now. It looks like Mintty ignores the blinking escape sequence (private mode 12) if you've set your default cursor preference to be blinking, so that's why it appears to be working. Emacs is still requesting that the cursor stop blinking, but Mintty is simply ignoring that request. > BTW, after I quit Emacs (and cursor stops blinking), restarting Emacs the cursor returns to blinking in Emacs; exiting one more time, it returns to stop blinking... That is exactly what I would expect. They're likely using the `cvvis` terminfo capability on startup (which enables cursor blinking), and the `cnorm` capability on shutdown (which disables blinking). The bottom line is that this is a duplicate of #10754 and is really an Emacs problem. You can probably work around it by editing your terminfo if you don't ever want applications to stop your cursor blinking.
claunia commented 2026-01-31 05:18:20 +00:00
Author
Owner
Copy Link

@angelog0 commented on GitHub (Feb 9, 2022):

If you execute tput cnorm in Mintty, does that disable blinking?

No...

@angelog0 commented on GitHub (Feb 9, 2022): > If you execute `tput cnorm` in Mintty, does that disable blinking? No...
claunia commented 2026-01-31 05:18:20 +00:00
Author
Owner
Copy Link

@Eli-Zaretskii commented on GitHub (Feb 10, 2022):

Is there a way of detecting whether the terminal cursor blinks? If so, Emacs could do that at startup.

@Eli-Zaretskii commented on GitHub (Feb 10, 2022): Is there a way of detecting whether the terminal cursor blinks? If so, Emacs could do that at startup.
claunia commented 2026-01-31 05:18:21 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Feb 10, 2022):

@Eli-Zaretskii There is an escape sequence which several terminals support that can be used to reset the cursor to the user's preference - both the shape and blinking. To see how that works, type printf "\e[ q" from a WSL shell.

Emacs is unlikely to use that, though, because I suspect they do everything through ncurses, but if they have the concept of shutdown script, you could maybe configure it to output that sequence yourself. That's what many vim users do.

@j4james commented on GitHub (Feb 10, 2022): @Eli-Zaretskii There is an escape sequence which several terminals support that can be used to reset the cursor to the user's preference - both the shape and blinking. To see how that works, type `printf "\e[ q"` from a WSL shell. Emacs is unlikely to use that, though, because I suspect they do everything through ncurses, but if they have the concept of shutdown script, you could maybe configure it to output that sequence yourself. That's what many vim users do.
claunia commented 2026-01-31 05:18:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 23, 2022):

Thanks for the investigation @j4james!

/dup #10754

@zadjii-msft commented on GitHub (Feb 23, 2022): Thanks for the investigation @j4james! /dup #10754
claunia commented 2026-01-31 05:18:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 23, 2022):

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 (Feb 23, 2022): 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!
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#16644
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?