starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Weird output log format when run gradle command #18748

New Issue
Closed
opened 2026-01-31 06:23:15 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:23:15 +00:00
Owner
Copy Link

Originally created by @zeroarst on GitHub (Oct 24, 2022).

Windows Terminal version

1.16.2641.0

Windows build number

10.0.19044.2130

Other Software

No response

Steps to reproduce

I have a andriod project and run ./gradle testDebugUnitTest. I assume any other gradle project that could run test[Variant]UnitTest should be able to reproudce the issue.
I can see it keeps printing prograss bar instead using the same one which messes up the log.

Expected Behavior

Tested in WIndows Command Prompt, the progress bar should display correct.
image

Actual Behavior

Looks like progress bar does not display correct.
image

Originally created by @zeroarst on GitHub (Oct 24, 2022). ### Windows Terminal version 1.16.2641.0 ### Windows build number 10.0.19044.2130 ### Other Software _No response_ ### Steps to reproduce I have a andriod project and run `./gradle testDebugUnitTest`. I assume any other gradle project that could run `test[Variant]UnitTest` should be able to reproudce the issue. I can see it keeps printing prograss bar instead using the same one which messes up the log. ### Expected Behavior Tested in WIndows Command Prompt, the progress bar should display correct. ![image](https://user-images.githubusercontent.com/1834837/197453625-01dc8319-48b2-4e9b-ad8b-1f26e610eaff.png) ### Actual Behavior Looks like progress bar does not display correct. ![image](https://user-images.githubusercontent.com/1834837/197453743-ae3f859c-f0d6-4aba-bf5a-f78c9641d26f.png)
claunia added the Issue-BugResolution-External labels 2026-01-31 06:23:15 +00:00
claunia commented 2026-01-31 06:23:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 24, 2022):

So, unfortunately, this is another instance of "client application is not using ENABLE_VIRTUAL_TERMINAL_PROCESSING". The terminal goes to great lengths to make sure that it's always enabled, but Gradle or the Java runtime or msys/cygwin is explicitly disabling it. There's nothing we can do when the application requests that it VT sequence processing be disabled (because it might be doing so for compatibility reasons.)

/dup https://github.com/gradle/gradle/issues/13279

@DHowett commented on GitHub (Oct 24, 2022): So, unfortunately, this is another instance of "client application is not using `ENABLE_VIRTUAL_TERMINAL_PROCESSING`". The terminal goes to _great_ lengths to make sure that it's always enabled, but Gradle or the Java runtime or msys/cygwin is **explicitly** disabling it. There's nothing we can do when the application requests that it VT sequence processing be disabled (because it might be doing so for compatibility reasons.) /dup https://github.com/gradle/gradle/issues/13279
claunia commented 2026-01-31 06:23:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 24, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Oct 24, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 06:23:18 +00:00
Author
Owner
Copy Link

@zeroarst commented on GitHub (Oct 25, 2022):

That issue is "colours are not escaped". But I don't see those colour code. Is it still the same issue?

@zeroarst commented on GitHub (Oct 25, 2022): That issue is "colours are not escaped". But I don't see those colour code. Is it still the same issue?
claunia commented 2026-01-31 06:23:18 +00:00
Author
Owner
Copy Link

@zeroarst commented on GitHub (Oct 25, 2022):

Looks like for now, adding TERM=cygwin to ./bashrc is the right solution in that link. Thanks.

@zeroarst commented on GitHub (Oct 25, 2022): Looks like for now, adding `TERM=cygwin` to `./bashrc` is the right solution in that link. 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 Issue-Bug Resolution-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#18748
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?