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

Buggy output display #18777

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

Originally created by @vertigo220 on GitHub (Oct 29, 2022).

Windows Terminal version

1.15.2874.0

Windows build number

Version 21H2 (OS Build 19044.2006)

Other Software

No response

Steps to reproduce

Not really sure what's going on here, but I've noticed issues before with the output getting messed up in Terminal in ways I've not experienced with Command Prompt or PowerShell. This is just one example, which happened in the past day, so I'll just provide a screenshot with red outlines over areas that are messed up and explanations of each, and hopefully somebody can figure out why this is happening, since it makes Terminal pretty much useless if users can't see an accurate command and output history. I'm fairly certain that when this happens, including this time, there usually aren't any issues initially, i.e. when the commands are issued, but rather when going back and looking at them later things are messed up, though in some cases it does happen in real-time.

The first commands I issued in this instance were as follows:

$var1="setup-v2.6.174.0"
$var2="BthPS32.6.174"
if ("$var2" -like "*$var1*") {echo 1; $var = ($var1 -split 'v?(.*)')[1]} else {if ("$var2" -match ($var1 -split '(\d.*\d)')[1]) {echo 2; $var = ($var1 -split '(\d.*\d)')[1]} else {if ("$var2" -match ($var1 -split '(\d[\d\.]*)\D*')[1]) {echo 3; $var = ($var1 -split '(\d\S*)\s*')[1]} else {if ($var2.replace('.','') -match ($var1 -split '(\d.*\d)')[1]) {echo 4; $dig_first = ($var1 -split '(\d)')[1]; $dig_last = ($var1 -split '.*(\d)')[1]; $var = ($var2 -split ".*[\sv-]($dig_first.*$dig_last)")[1]} else {if ($var2.replace('.','') -match ($var1 -split '(\d[\d\.]*)\D')[1]) {echo 5; $dig_first = ($var1 -split '(\d)')[1]; $dig_last = ($var1 -split '.*(\d)')[1]; $var = ($var2 -split ".*[\sv-]($dig_first.*$dig_last)")[1]} else {echo "no match (1)"; $var = ""}}}}};
$var1="BthPS3 Bluetooth Drivers v2.6.174"

As you can see, the first command isn't even there, and after the second command there's no prompt and the beginning of the third command is cut off (so the prompt and the first 96 characters are missing). The next box shows that the output from the command is missing entirely, going straight from the input of the command to the next prompt. Next you can see it shows the output of a command (an empty line, the number 3, another empty line, the number 2.6, then the number 174) and then immediately shows the output of one or two other commands despite the commands themselves not showing. Finally, there's the command "$var2" which I entered, at which point it displayed the variable's contents, but then when I went to repeat a previous command from history, it put "$var2" on the command line again and I couldn't get rid of it, and it showed the history commands as I cycled through them on the next line with empty space where the prompt normally is (this happened as I was doing it).

So trying to scroll up to look back at what I've done and the results each command has given me and what each variable was set to along the way is impossible, since things are cut off or completely left out. It's unusable like this and means I need to stick with the standard terminals to get any serious work done.

Screenshot_22-10-29_13 15 34-WindowsTerminal

Expected Behavior

No response

Actual Behavior

See above

Originally created by @vertigo220 on GitHub (Oct 29, 2022). ### Windows Terminal version 1.15.2874.0 ### Windows build number Version 21H2 (OS Build 19044.2006) ### Other Software _No response_ ### Steps to reproduce Not really sure what's going on here, but I've noticed issues before with the output getting messed up in Terminal in ways I've not experienced with Command Prompt or PowerShell. This is just one example, which happened in the past day, so I'll just provide a screenshot with red outlines over areas that are messed up and explanations of each, and hopefully somebody can figure out why this is happening, since it makes Terminal pretty much useless if users can't see an accurate command and output history. I'm fairly certain that when this happens, including this time, there usually aren't any issues initially, i.e. when the commands are issued, but rather when going back and looking at them later things are messed up, though in some cases it does happen in real-time. The first commands I issued in this instance were as follows: ``` $var1="setup-v2.6.174.0" $var2="BthPS32.6.174" if ("$var2" -like "*$var1*") {echo 1; $var = ($var1 -split 'v?(.*)')[1]} else {if ("$var2" -match ($var1 -split '(\d.*\d)')[1]) {echo 2; $var = ($var1 -split '(\d.*\d)')[1]} else {if ("$var2" -match ($var1 -split '(\d[\d\.]*)\D*')[1]) {echo 3; $var = ($var1 -split '(\d\S*)\s*')[1]} else {if ($var2.replace('.','') -match ($var1 -split '(\d.*\d)')[1]) {echo 4; $dig_first = ($var1 -split '(\d)')[1]; $dig_last = ($var1 -split '.*(\d)')[1]; $var = ($var2 -split ".*[\sv-]($dig_first.*$dig_last)")[1]} else {if ($var2.replace('.','') -match ($var1 -split '(\d[\d\.]*)\D')[1]) {echo 5; $dig_first = ($var1 -split '(\d)')[1]; $dig_last = ($var1 -split '.*(\d)')[1]; $var = ($var2 -split ".*[\sv-]($dig_first.*$dig_last)")[1]} else {echo "no match (1)"; $var = ""}}}}}; $var1="BthPS3 Bluetooth Drivers v2.6.174" ``` As you can see, the first command isn't even there, and after the second command there's no prompt and the beginning of the third command is cut off (so the prompt and the first 96 characters are missing). The next box shows that the output from the command is missing entirely, going straight from the input of the command to the next prompt. Next you can see it shows the output of a command (an empty line, the number 3, another empty line, the number 2.6, then the number 174) and then immediately shows the output of one or two other commands despite the commands themselves not showing. Finally, there's the command "$var2" which I entered, at which point it displayed the variable's contents, but then when I went to repeat a previous command from history, it put "$var2" on the command line again and I couldn't get rid of it, and it showed the history commands as I cycled through them on the next line with empty space where the prompt normally is (this happened as I was doing it). So trying to scroll up to look back at what I've done and the results each command has given me and what each variable was set to along the way is impossible, since things are cut off or completely left out. It's unusable like this and means I need to stick with the standard terminals to get any serious work done. ![Screenshot_22-10-29_13 15 34-WindowsTerminal](https://user-images.githubusercontent.com/12024557/198848841-05984f87-9878-4287-81fb-d2df01edb9d6.png) ### Expected Behavior _No response_ ### Actual Behavior See above
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 Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity 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#18777
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?