colornames that start with "pale" get confused with "palette"

[Elaine Meng]

Colornames that start with "pale" get mixed up with the "palette" keyword of the "color" command. So although you can use other color names with spaces in them without quoting, you must either use quotes or smush the words in the colorname together. So, the first example here won't work because it tries to fetch a palette, but the others will:

color /b pale green
color /b "pale green"
color /b palegreen

I imagine it is low priority, just thought I should record this observation.

[goddard@…]

Any suggestion for fixing this?  I think the solution is to use palegreen.  Having spaces in arguments unfortunately leads to many problems as we have seen with atom specs.

[Eric Pettersen]

According to usage, the 'palette' keyword would follow a color name. I thought color-name parsing was supposed to be "greedy", just like atom specs. If it were, it should find "pale green" as a color name before it begins to look for the "palette" keyword. Seems like a bug to me.

[Greg Couch]

Unless the argument is a required positional argument, keywords are checked first. And optional positional arguments can be specified as a keyword argument. So the unambigious command is:

color /b color pale green

[Eric Pettersen]

Milestone renamed

[Elaine Meng]

Implementing #969 (color subcommands) is expected to circumvent this problem.

[Greg Couch]

Fixed by fixe to #969.