starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Less.exe colors break after any other output is written #5854

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

Originally created by @adam-c-anderson on GitHub (Jan 10, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.7.3451.0

Any other software? `less` installed from Chocolatey. `choco install less`.

Steps to reproduce

  1. Open a new PS terminal session. I'm able to reproduce this with an empty profile.
  2. View some output from less. less -? is quick and easy but anything will do. Less outputs help with expected normal/foreground color (gray or white)
  3. Do something that causes output. I used ls but type also works. The output appears as normal.
  4. Now view some output from less again. e.g. less -? again

Expected behavior

less normal output should appear as before with a gray/white foreground color

Actual behavior

less normal output uses black as the foreground color, rendering it illegible on dark backgrounds. This only occurs in Windows Terminal. The normal console host does not reproduce this problem.

Originally created by @adam-c-anderson on GitHub (Jan 10, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.7.3451.0 Any other software? `less` installed from Chocolatey. `choco install less`. ``` # Steps to reproduce 1. Open a new PS terminal session. I'm able to reproduce this with an empty profile. 2. View some output from less. `less -?` is quick and easy but anything will do. Less outputs help with expected normal/foreground color (gray or white) 3. Do something that causes output. I used `ls` but `type` also works. The output appears as normal. 4. Now view some output from less again. e.g. `less -?` again # Expected behavior `less` normal output should appear as before with a gray/white foreground color # Actual behavior `less` normal output uses black as the foreground color, rendering it illegible on dark backgrounds. This only occurs in Windows Terminal. The normal console host does not reproduce this problem.
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixTracking-External labels 2026-01-31 00:23:29 +00:00
claunia commented 2026-01-31 00:23:30 +00:00
Author
Owner
Copy Link

@lzybkr commented on GitHub (Jan 10, 2020):

I think you're hitting a problem in less.exe which I've fixed. My fix was merged but I don't think it was released yet. You can see the fix and get a pre-built binary here.

@lzybkr commented on GitHub (Jan 10, 2020): I think you're hitting a problem in `less.exe` which I've fixed. My fix was merged but I don't think it was released yet. You can see the fix and get a pre-built binary [here](https://github.com/lzybkr/less/releases/tag/fix_windows_vt).
claunia commented 2026-01-31 00:23:30 +00:00
Author
Owner
Copy Link

@adam-c-anderson commented on GitHub (Jan 10, 2020):

Interesting. FWIW, the less that comes installed with Git for Windows does not seem to exhibit the same problem. I.e.

> & 'C:\Program Files\Git\usr\bin\less.exe' -?
> ls
> & 'C:\Program Files\Git\usr\bin\less.exe' -?

outputs help text with the desired light FG color while the same steps with C:\ProgramData\chocolatey\bin\less.exe outputs with black FG on the second invocation. I hope your fix gets accepted and released soon!

@adam-c-anderson commented on GitHub (Jan 10, 2020): Interesting. FWIW, the `less` that comes installed with Git for Windows does not seem to exhibit the same problem. I.e. ```ps1 > & 'C:\Program Files\Git\usr\bin\less.exe' -? > ls > & 'C:\Program Files\Git\usr\bin\less.exe' -? ``` outputs help text with the desired light FG color while the same steps with `C:\ProgramData\chocolatey\bin\less.exe` outputs with black FG on the second invocation. I hope your fix gets accepted and released soon!
claunia commented 2026-01-31 00:23:30 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 13, 2020):

I'm going to close this one out, actually. Further discussion about less, specifically, should be had at https://github.com/gwsw/less/pull/29. Thanks!

@DHowett-MSFT commented on GitHub (Jan 13, 2020): I'm going to close this one out, actually. Further discussion about less, specifically, should be had at https://github.com/gwsw/less/pull/29. 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 Needs-Tag-Fix Needs-Triage Resolution-External 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#5854
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?