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

When changing focus the cursor has significant delay before appearing. #5276

New Issue
Closed
opened 2026-01-31 00:09:25 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:09:25 +00:00
Owner
Copy Link

Originally created by @bradphelan on GitHub (Nov 28, 2019).

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal (Preview)
Version: 0.7.3291.0

Steps to reproduce

Setup keybindings to change focus. For example

    , {"command": "moveFocusLeft", "keys": ["alt+h"]}
    , {"command": "moveFocusRight", "keys": ["alt+l"]}
    , {"command": "moveFocusUp", "keys": ["alt+k"]}
    , {"command": "moveFocusDown", "keys": ["alt+j"]}

Expected behavior

As soon as I change focus to another pane the cursor should immediately appear in the newly focused pane.

Actual behavior

There is a delay.

If I change focus quickly multiple times using the keybinding it is hard for the eye to track where to focus because the cursor does not ever appear until you stop pressing the focus change key.

There is also the pane border color change on focus but for some reason the color contrast there is difficult for me to track. I prefer to look for the cursor.

What I think is happening is that when you change focus to a new pane the cursor blink state machine starts again from zero and zero is the off state.

A fix might be to have the zero state of the cursor to be on rather than off.

With the mouse

The same problem happens when focusing the pane with the mouse. There is a delay.

Other Applications

I've noticed that the old power shell console and cmd.exe console seem to have the same probem.

gvim seems to get it right. Switching text editing panes quickly shows the cursor immediately.

Originally created by @bradphelan on GitHub (Nov 28, 2019). # Environment ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal (Preview) Version: 0.7.3291.0 ``` # Steps to reproduce Setup keybindings to change focus. For example ``` , {"command": "moveFocusLeft", "keys": ["alt+h"]} , {"command": "moveFocusRight", "keys": ["alt+l"]} , {"command": "moveFocusUp", "keys": ["alt+k"]} , {"command": "moveFocusDown", "keys": ["alt+j"]} ``` # Expected behavior As soon as I change focus to another pane the cursor should **immediately** appear in the newly focused pane. # Actual behavior There is a delay. If I change focus quickly multiple times using the keybinding it is hard for the eye to track where to focus because the cursor **does not** ever appear until you stop pressing the focus change key. There is also the pane border color change on focus but for some reason the color contrast there is difficult for me to track. I prefer to look for the cursor. What I think is happening is that when you change focus to a new pane the cursor blink state machine starts again from zero and zero is the off state. A fix might be to have the zero state of the cursor to be on rather than off. # With the mouse The same problem happens when focusing the pane with the mouse. There is a delay. # Other Applications I've noticed that the old power shell console and cmd.exe console seem to have the same probem. gvim seems to get it right. Switching text editing panes quickly shows the cursor immediately.
claunia commented 2026-01-31 00:09:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 30, 2019):

Good catch. Thanks!

@DHowett-MSFT commented on GitHub (Nov 30, 2019): Good catch. Thanks!
claunia commented 2026-01-31 00:09:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 14, 2020):

:tada:This issue was addressed in #4032, which has now been successfully released as Windows Terminal Preview v0.8.10091.0.🎉

Handy links:

@ghost commented on GitHub (Jan 14, 2020): :tada:This issue was addressed in #4032, which has now been successfully released as `Windows Terminal Preview v0.8.10091.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.8.10091.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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 Area-TerminalControl Area-UserInterface Help Wanted Issue-Bug Priority-3 Product-Terminal Resolution-Fix-Committed
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#5276
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?