Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Colors break in Windows Terminal #42

Closed
adam-c-anderson opened this issue Jan 10, 2020 · 7 comments
Closed

Colors break in Windows Terminal #42

adam-c-anderson opened this issue Jan 10, 2020 · 7 comments

Comments

@adam-c-anderson
Copy link

OS: Win10 Pro 10.0.18363.0
Windows Terminal 0.7.3451.0

Steps to reproduce:

  1. Open a new PS terminal session. I am able to reproduce this issue 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.

Expected: normal output should use the same color as before
Actual: normal output appears black

This only occurs in Windows Terminal. The normal console host does not reproduce this problem. I'm not sure if it's a Windows Terminal bug or less. I've reported it in the Windows Terminal repo as well.

@lzybkr
Copy link
Contributor

lzybkr commented Jan 13, 2020

This issue is more likely fixed in #26

@tats-u
Copy link

tats-u commented Jan 19, 2020

@lzybkr
I have a similar issue in the version 551, which is available in scoop.
OS: Windows 10 Pro 18363.592
Terminal: Hyper 3.0.2 + Dark theme plugins (hyper-material / hyper-solarized-dark / verminal)

Has it already been fixed after the version 551? If so, do you know when the next release will be published? Releases has been stopped at it as much as about half a year ago.

@rivy
Copy link

rivy commented Jan 27, 2020

I believe this is already fixed in my "fork" (https://github.com/rivy/less).
It's usable until a/the fix is released here...

@gwsw
Copy link
Owner

gwsw commented Mar 13, 2020

Should be fixed in #26.

@gwsw gwsw closed this as completed Mar 13, 2020
@tats-u
Copy link

tats-u commented Mar 13, 2020

Oh, version 553 & 554, which seem to have fixed this bug, are available in GitHub Releases. I'm sorry for overlooking them. However, they have not been mentioned in the official homepage... Are they tolerable against general use like version 551? If so, I'd like to encourage Chocolatey and Scoop, package managers of Windows softwares, to update the packages of less.

@gwsw
Copy link
Owner

gwsw commented Mar 14, 2020

Versions 553 & 554 have not yet gone through beta testing, so I'd prefer they not get general use yet. I plan to release a version for beta testing soon.

@tats-u
Copy link

tats-u commented Mar 15, 2020

@gwsw Thank you for the information. I'll wait for one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants