Currently this does not allow for users to define any colors other than the basics:

• magenta
• red
• yellow
• green
• blue
• cyan

and have them show up correctly in the terminal. Another option (which I feel would be better and would also allow us to continue supporting the default configuration) would be to add a terminalColor property to the maniphest.priorities config and allowing the user to define a color that will be displayed on phabricator and a color that arc tasks will display.

If you think this is a better option, let me know and I will close this diff and make another one with those changes instead. Thanks for your help!

I think doing terminalColor is probably overkill, but maybe it's worth it to map the web colors to terminal colors? Specifically, this is my best effort at producing such a map offhand:

$web_to_terminal = array(
  'red' => 'red',
  'orange' => 'orange', // Or red? Is orange a terminal color?
  'yellow' => 'yellow',
  'green' => 'green', 
  'blue' => 'blue',
  'sky' => 'cyan',
  'indigo' => 'magenta',
  'violet' => 'magenta',
);

Then send anything else to white? Does that seem reasonable? I think that should be the best we can do in all reasonable cases, without requiring additional configuration.

Actually I like that idea a lot. I can see how terminalColor could be overkill. But I like the web color map. Would you like to to just map the default configuration colors, or would you like me to map basic ones as well? I will get to work on that right now.

The web config should only support a subset of colors -- basically the ones here, under the "Colors" header:

https://secure.phabricator.com/uiexample/view/PHUIColorPalletteExample/

It doesn't (IIRC) support arbitrary web/HTML colors, so there's no need to map anything not on the palette page. I think the most-ambitious version of this patch would just map the "light" colors, too.