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

command-line options not visible when using PowerShell with Solarized Dark color scheme #6716

Closed
imwithsam opened this issue Jun 29, 2020 · 5 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@imwithsam
Copy link

Environment

Windows build number: 10.0.19041.0
Windows Terminal version: 1.0.1401.0

Any other software? PowerShell 7.0.2 and 5.1.19041.1

Steps to reproduce

  1. Set the Windows Terminal color scheme to 'Solarized Dark'
  2. Bring up PowerShell in Windows Terminal
  3. Type any command with an option (e.g. git help -a)

Expected behavior

You can read the entire command line (e.g. git help -a)

Actual behavior

You cannot read the command-line option (e.g. git help is visible but -a is not)

Notes

As far as I can tell, this issue appears to be specific to Windows Terminal with PowerShell and the Solarized Dark color scheme.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 29, 2020
@Phistr90
Copy link

I have the same problem

@abjklk
Copy link

abjklk commented Jul 1, 2020

The issue is with the present colorScheme values as evident in the defaults.json file.
The attributes brightBlack and background have the same hex value of #002B36

A temporary fix would be to create your own custom Solarized Dark color scheme.
Follow this documentation to create a custom theme: https://docs.microsoft.com/en-us/windows/terminal/customize-settings/color-schemes

@zadjii-msft
Copy link
Member

Thanks for the suggestion! Please make sure to search for duplicates when filing new issues. This has been reported a bunch of times already - I think we all regret shipping Solarized as a default theme.

/dup #6696 #6424 #6390 #6286 #6283 #6208 #6121 #6061 #5896, and a ton more. Resolved by #6617 #6618 #6489 (all three are currently in review)

@ghost
Copy link

ghost commented Jul 6, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 6, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 6, 2020
@imwithsam
Copy link
Author

I searched for duplicates but only in Open issues. Thank you for the update!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants