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

sp; mf ... leaves cursor visible in the inactive pane #22203

New Issue
Open
opened 2026-01-31 08:06:21 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 08:06:21 +00:00
Owner
Copy Link

Originally created by @vefatica on GitHub (Sep 3, 2024).

When I, for example, wt sp cmd.exe; mf 1, the cursor remains visible in the inactive pane. This is unlike moving focus in other situations; normally the cursor is hidden in an inactive pane.

Originally created by @vefatica on GitHub (Sep 3, 2024). When I, for example, `wt sp cmd.exe; mf 1`, the cursor remains visible in the inactive pane. This is unlike moving focus in other situations; normally the cursor is hidden in an inactive pane.
claunia added the Issue-BugPriority-3Product-TerminalArea-TerminalControl labels 2026-01-31 08:06:22 +00:00
claunia commented 2026-01-31 08:06:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 3, 2024):

Version number?

@zadjii-msft commented on GitHub (Sep 3, 2024): Version number?
claunia commented 2026-01-31 08:06:22 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 3, 2024):

That was the 20 release and the 21 preview. I just updated and the same is true of WindowsTerminal 1.22.2408.23002 (preview) and WindowsTerminal 1.21.2408.23001.

And I'm seeing this for the first time when starting the 1.21 release.

image

That's apparently from

        {
            "id": null,
            "keys": "ctrl+shift+w"
        },

Any idea?

@vefatica commented on GitHub (Sep 3, 2024): That was the 20 release and the 21 preview. I just updated and the same is true of WindowsTerminal 1.22.2408.23002 (preview) and WindowsTerminal 1.21.2408.23001. And I'm seeing this for the first time when starting the 1.21 release. ![image](https://github.com/user-attachments/assets/d85b1b6b-2e17-430e-844a-953851542ab4) That's apparently from ``` { "id": null, "keys": "ctrl+shift+w" }, ``` Any idea?
claunia commented 2026-01-31 08:06:23 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 9, 2024):

When I, for example, wt sp cmd.exe; mf 1, the cursor remains visible in the inactive pane. This is unlike moving focus in other situations; normally the cursor is hidden in an inactive pane.

Any more on this?

@vefatica commented on GitHub (Sep 9, 2024): > When I, for example, wt sp cmd.exe; mf 1, the cursor remains visible in the inactive pane. This is unlike moving focus in other situations; normally the cursor is hidden in an inactive pane. Any more on this?
claunia commented 2026-01-31 08:06:23 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 14, 2024):

If you have looked into this you've probably figured out that it's a matter of timing. I can reproduce the undesirable behavior (cursor showing in the inactive pane) with simulated keystrokes (using TCC's KEYSTACK command).

keystack alt-shift-+ alt-left

If I introduce a delay (9/18 second below) before moving focus, the cursor is not showing in the inactive pane.

keystack alt-shift-+ /w9 alt-left

@vefatica commented on GitHub (Sep 14, 2024): If you have looked into this you've probably figured out that it's a matter of timing. I can reproduce the undesirable behavior (cursor showing in the inactive pane) with simulated keystrokes (using TCC's KEYSTACK command). `keystack alt-shift-+ alt-left` If I introduce a delay (9/18 second below) before moving focus, the cursor is not showing in the inactive pane. `keystack alt-shift-+ /w9 alt-left`
claunia commented 2026-01-31 08:06:23 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 16, 2024):

And I'm seeing this for the first time when starting the 1.21 release.

Is the null from you or automatically generated by us? I'm assuming the latter. In that case I think it's a bug in #17162 and I suppose we fail to remove bindings that have no action?

@lhecker commented on GitHub (Sep 16, 2024): > And I'm seeing this for the first time when starting the 1.21 release. Is the `null` from you or automatically generated by us? I'm assuming the latter. In that case I think it's a bug in #17162 and I suppose we fail to remove bindings that have no action?
claunia commented 2026-01-31 08:06:24 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 16, 2024):

I believe this issue also happens even if all you do is unfocus the application, while the terminal is currently busy with processing output that doesn't move the cursor (= pure VT).

DispatchTimer::Stop neither cancels the pending nor blocks until the queued event is done:

If Stop is called when the timer interval has just elapsed, it's possible that the timer already queued a Tick event. This event will still be raised.

So, when we do "stop the timer, then disable the cursor", we may still get a blink tick.

@lhecker commented on GitHub (Sep 16, 2024): I believe this issue also happens even if all you do is unfocus the application, while the terminal is currently busy with processing output that doesn't move the cursor (= pure VT). `DispatchTimer::Stop` neither cancels the pending nor blocks until the queued event is done: > If Stop is called when the timer interval has just elapsed, it's possible that the timer already queued a Tick event. This event will still be raised. So, when we do "stop the timer, then disable the cursor", we may still get a blink tick.
claunia commented 2026-01-31 08:06:24 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 18, 2024):

I don't think I put that null in there.

@vefatica commented on GitHub (Sep 18, 2024): I don't think I put that `null` in there.
claunia commented 2026-01-31 08:06:25 +00:00
Author
Owner
Copy Link

@vefatica commented on GitHub (Sep 18, 2024):

I found other ways to leave the cursor showing in an inactive pane also. One is to just do the keystrokes quickly enough ... Alt-Shift-+, Alt-Left.

@vefatica commented on GitHub (Sep 18, 2024): I found other ways to leave the cursor showing in an inactive pane also. One is to just do the keystrokes quickly enough ... Alt-Shift-+, Alt-Left.
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 Issue-Bug Priority-3 Product-Terminal
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#22203
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?