PSRL 2.0.0-beta2 not setting defaults for OperatorColor and ParameterColor
See original GitHub issueEnvironment data
PS version: 6.1.0-preview.4
PSReadline version: 2.0.0-beta2
os: Linux HILLR2 4.4.0-18204-Microsoft #1001-Microsoft Sat Jul 21 16:57:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux
PS file version:
Steps to reproduce or exception report
-
Install powershell-preview (6.1.0-p4) on Ubuntu 18.04 running in WSL (Windows 10 1803)
-
Run pwsh-preview and type in a command with a parameter and you won’t see the
-Name
in this case:
Here’s why -
Note how both the OperatorColor and ParameterColor have not been set to a default. Hmm, just repro’d this on Windows 10 itself with 6.1.0-p4 installed. Is this an issue with how PowerShell configures PSRL? Or a problem with PSRL’s defaults? Or is this supposed to work with those two values not set?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That might help a little, but I think more often the problem will be having colors that are too similar, and there is no portable way to determine the RGB values for the standard colors.
Maybe one fix would be to check every default “foreground” color to make sure it isn’t the same as the current “background” color. And if so, adjust to another color that is different than the background color. And if on a VT system, maybe even use a computed contrast 8bit color.