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

yazi not working in Preview v1.22.2362.0 #22183

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

Originally created by @doongjohn on GitHub (Aug 29, 2024).

Windows Terminal version

1.22.2362.0

Windows build number

10.0.22631.4037

Other Software

yazi 0.3.2 https://github.com/sxyazi/yazi/releases/tag/v0.3.2

Steps to reproduce

Run yazi in any shell (powershell, cmd, nu, ...)

Expected Behavior

It should work. It works in Preview v1.21.1772.0

Actual Behavior

  1. It takes a while to start yazi.
  2. When it opens, yazi is not responding to any input.
Originally created by @doongjohn on GitHub (Aug 29, 2024). ### Windows Terminal version 1.22.2362.0 ### Windows build number 10.0.22631.4037 ### Other Software yazi 0.3.2 <https://github.com/sxyazi/yazi/releases/tag/v0.3.2> ### Steps to reproduce Run yazi in any shell (powershell, cmd, nu, ...) ### Expected Behavior It should work. It works in [Preview v1.21.1772.0](https://github.com/microsoft/terminal/releases/tag/v1.21.1772.0) ### Actual Behavior 1. It takes a while to start yazi. 2. When it opens, yazi is not responding to any input.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:05:51 +00:00
claunia commented 2026-01-31 08:05:52 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Aug 29, 2024):

I think this is possibly another case of #17813. If I run yazi with the debug tap, I can see it sending a DA1 request, and I can see Windows Terminal responding, but yazi is clearly not receiving that response, because you see it waiting for a couple of seconds before it times out and proceeds with other queries.

And from a brief scan of the crossterm source (which I think is what yazi is using), I can see they are setting the ENABLE_VIRTUAL_TERMINAL_PROCESSING mode, but not the ENABLE_VIRTUAL_TERMINAL_INPUT mode.

That said, I'm not entirely sure what's happening after it as started up. I suspect that might be related to win32-input-mode somehow, because if I type in the debug pane (which sends through basic VT input sequences), I can get yazi to respond. It's only when Windows Terminal is sending the win32-input-mode sequences that it fails to respond.

@j4james commented on GitHub (Aug 29, 2024): I think this is possibly another case of #17813. If I run yazi with the debug tap, I can see it sending a `DA1` request, and I can see Windows Terminal responding, but yazi is clearly not receiving that response, because you see it waiting for a couple of seconds before it times out and proceeds with other queries. And from a brief scan of the [crossterm](https://github.com/crossterm-rs/crossterm) source (which I think is what yazi is using), I can see they are setting the `ENABLE_VIRTUAL_TERMINAL_PROCESSING` mode, but not the `ENABLE_VIRTUAL_TERMINAL_INPUT` mode. That said, I'm not entirely sure what's happening after it as started up. I suspect that might be related to win32-input-mode somehow, because if I type in the debug pane (which sends through basic VT input sequences), I can get yazi to respond. It's only when Windows Terminal is sending the win32-input-mode sequences that it fails to respond.
claunia commented 2026-01-31 08:05:52 +00:00
Author
Owner
Copy Link

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

I'll be closing this as a duplicate of #17813. (Thanks for the report though!) I tested this with #17833 and it seems to work now. /dup #17813

@lhecker commented on GitHub (Sep 3, 2024): I'll be closing this as a duplicate of #17813. (Thanks for the report though!) I tested this with #17833 and it seems to work now. /dup #17813
claunia commented 2026-01-31 08:05:52 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 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#22183
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?