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

Output lines are not always continuous with MSYS2 tree.exe #15636

New Issue
Open
opened 2026-01-31 04:44:04 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:44:04 +00:00
Owner
Copy Link

Originally created by @matteocoder on GitHub (Oct 21, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal 1.10.2714 on Microsoft Windows [Version 10.0.19043.1288]

Other Software

tree v1.8.0, bash 4.4.23(1)-release, both of which run within the MSYS2 environment installed by Git-for-Windows.

Steps to reproduce

  1. Download tree.exe from here, extract it and make sure that it can be called from the terminal;
  2. Locate a directory that contains a multitude of files and subdirectories (I will be using the Windows Terminal repo as an example);
  3. run $ tree path/to/directory/

Expected Behavior

The output lines on the left should be continuous.

Actual Behavior

Sometimes there are small gaps between the output lines.

Here are two screenshots comparing the output from Windows Terminal and the output from MinTTY:

Windows Terminal:
treewinterm

MinTTY:
treemintty

Originally created by @matteocoder on GitHub (Oct 21, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal 1.10.2714 on Microsoft Windows [Version 10.0.19043.1288] ### Other Software tree v1.8.0, bash 4.4.23(1)-release, both of which run within the MSYS2 environment installed by Git-for-Windows. ### Steps to reproduce 1. Download tree.exe from [here](https://mirror.msys2.org/msys/x86_64/tree-1.8.0-1-x86_64.pkg.tar.xz), extract it and make sure that it can be called from the terminal; 2. Locate a directory that contains a multitude of files and subdirectories (I will be using the Windows Terminal repo as an example); 3. run `$ tree path/to/directory/` ### Expected Behavior The output lines on the left should be continuous. ### Actual Behavior Sometimes there are small gaps between the output lines. Here are two screenshots comparing the output from Windows Terminal and the output from MinTTY: Windows Terminal: ![treewinterm](https://user-images.githubusercontent.com/22897138/138342020-e1d9296f-eba6-4516-a976-c21622f4ebc4.JPG) MinTTY: ![treemintty](https://user-images.githubusercontent.com/22897138/138342054-b2abe6cf-3782-440e-bf9d-32e558cebce4.JPG)
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-Rendering Needs-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Tracking-External
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#15636
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?