Not all color names give right color?

Am I color blind, or is "DarkYellow" coming out as very light gray (even
lighter than "Yellow") in PowerShell, impossible to read on a white
background?


And BTW, why this set of color names?

Things could have been a easier to remember if they had used the predefined
set from the .Net framework and from HTML, or at least applied the same
names to a subset thereof.

In .Net and HTML there's no "darkyellow", but you can say "olive" to get
color #808000, which is what I suspected they meant by "darkyellow" in PS.

> Am I color blind, or is "DarkYellow" coming out as very light gray (even
> lighter than "Yellow") in PowerShell, impossible to read on a white
> background?
>
>
> And BTW, why this set of color names?
>
> Things could have been a easier to remember if they had used the predefined
> set from the .Net framework and from HTML, or at least applied the same
> names to a subset thereof.
>

> In .Net and HTML there's no "darkyellow", but you can say "olive" to get
> color #808000, which is what I suspected they meant by "darkyellow" in PS.

See my post here :

http://groups.google.be/group/micros...e=source&hl=fr

Regards,

--
Jean - JMST
Belgium

On Wed, 08 Nov 2006 10:36:12 +0100, Jean <repondre@groupe.svp> wrote:

> > Am I color blind, or is "DarkYellow" coming out as very light gray (even
> > lighter than "Yellow") in PowerShell, impossible to read on a white
> > background?
> >
> >
> > And BTW, why this set of color names?
> >
> > Things could have been a easier to remember if they had used the predefined
> > set from the .Net framework and from HTML, or at least applied the same
> > names to a subset thereof.
> >
>
> > In .Net and HTML there's no "darkyellow", but you can say "olive" to get
> > color #808000, which is what I suspected they meant by "darkyellow" in PS.
>
> See my post here :
>
> http://groups.google.be/group/micros...e=source&hl=fr
>
> Regards,

Thanks, that explains a lot.

The color positions corresponding to DarkMagenta and DarkYellow have been
"pre-personalized" in the shortcut created by the PS installer, but if you
create a new shortcut to powershell.exe they're back at their defaults and
the names match what you get to see.

> On Wed, 08 Nov 2006 10:36:12 +0100, Jean <repondre@groupe.svp> wrote:
>
>>> Am I color blind, or is "DarkYellow" coming out as very light gray (even
>>> lighter than "Yellow") in PowerShell, impossible to read on a white
>>> background?
>>>
>>>
>>> And BTW, why this set of color names?
>>>
>>> Things could have been a easier to remember if they had used the predefined
>>> set from the .Net framework and from HTML, or at least applied the same
>>> names to a subset thereof.
>>>
>>
>>> In .Net and HTML there's no "darkyellow", but you can say "olive" to get
>>> color #808000, which is what I suspected they meant by "darkyellow" in PS.
>>
>> See my post here :
>>
>>
>> http://groups.google.be/group/micros...e=source&hl=fr
>>
>> Regards,
>
> Thanks, that explains a lot.
>
> The color positions corresponding to DarkMagenta and DarkYellow have been
> "pre-personalized" in the shortcut created by the PS installer, but if you
> create a new shortcut to powershell.exe they're back at their defaults and
> the names match what you get to see.

Yes :-)
For clarity I've just made some images :
http://automation.eu.tf/console_colors.htm

Regards neighbor,

--
Jean - JMST
Belgium