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

mc is slower and shows artifacts #2307

New Issue
Closed
opened 2026-01-30 22:52:00 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:52:00 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Jun 27, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]   
Windows Terminal version (if applicable): 0.2.1715.0

Screen 1920x1200
default settings for windows terminal

Steps to reproduce

  1. open Windows Terminal

  2. ssh in any shell session (tested pwsh, cmd, bash) to linux server

  3. start mc (midnight commander)

  4. scroll through folder list with arrow down/up

  5. do the same as above in pwsh or bash or cmd but started directly (without Windows Terminal)

  6. Compare performance and screen quality

Expected behavior

Performance and stability should be at least the same in both cases

Actual behavior

Windows Terminal scenario is noticeably slower.
Windows terminal blinks with artifacts (mostly |) on each scroll step when you press and hold up/down key.

Tested the same with mc in local bash session. Less artifacts and a bit improved speed but still noticable slowdown.

Seems related but not duplicate of #117

Originally created by @ghost on GitHub (Jun 27, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.175] Windows Terminal version (if applicable): 0.2.1715.0 Screen 1920x1200 default settings for windows terminal ``` # Steps to reproduce 0. open Windows Terminal 1. ssh in any shell session (tested pwsh, cmd, bash) to linux server 2. start mc (midnight commander) 3. scroll through folder list with arrow down/up 4. do the same as above in pwsh or bash or cmd but started directly (without Windows Terminal) 5. Compare performance and screen quality # Expected behavior Performance and stability should be at least the same in both cases # Actual behavior Windows Terminal scenario is noticeably slower. Windows terminal blinks with artifacts (mostly ``|``) on each scroll step when you press and hold up/down key. Tested the same with mc in local bash session. Less artifacts and a bit improved speed but still noticable slowdown. Seems related but not duplicate of #117
claunia commented 2026-01-30 22:52:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 17, 2020):

For whatever reason, this issue is weirdly bugged and not showing up in the query I've been using to triage 1.0 issues.

Thant being said, I'm thinking that this is something that's going to hopefully just magically get fixed with #778/#5185/#5345 getting merged, whenever that does.

@zadjii-msft commented on GitHub (Apr 17, 2020): For whatever reason, this issue is weirdly bugged and not showing up in the [query I've been using](https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Terminal+v1.0%22+no%3Aassignee+-label%3AIn-PR+-label%3AIssue-Docs) to triage [1.0 issues](https://github.com/microsoft/terminal/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Terminal+v1.0%22). Thant being said, I'm thinking that this is something that's going to hopefully just magically get fixed with #778/#5185/#5345 getting merged, whenever that does.
claunia commented 2026-01-30 22:52:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 22, 2020):

This was reported in 0.2, actually, before we ironed out some pty issues and some UTF-8 parsing issues that may have resulted in us corrupting things coming out of the client application. I'm going to close this one out, since it doesn't seem to repro any more (at least for me :P) and the speed seems entirely acceptable.

Thanks!

@DHowett-MSFT commented on GitHub (Apr 22, 2020): This was reported in 0.2, actually, before we ironed out some pty issues and some UTF-8 parsing issues that may have resulted in us corrupting things coming out of the client application. I'm going to close this one out, since it doesn't seem to repro any more (at least for me :P) and the speed seems entirely acceptable. Thanks!
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-Performance Issue-Bug Needs-Tag-Fix Product-Conhost Product-Terminal Resolution-No-Repro
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#2307
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?