Closed (won't fix)
Project:
Drush
Version:
8.x-6.x-dev
Component:
Core Commands
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Nov 2012 at 12:59 UTC
Updated:
15 Sep 2013 at 23:27 UTC
hard to see whether or not an option is select. The (selected) word is not that clear, especially since we can use colors.
pof attached.
| Comment | File | Size | Author |
|---|---|---|---|
| drush-colorized-multichoice.patch | 1.4 KB | drzraf |
Comments
Comment #1
greg.1.anderson commentedThis issue was marked
closed (won't fix)because Drush has moved to Github.If this feature is still desired, you may copy it to our Github project. For best results, create a Pull Request that has been updated for the master branch. Post a link here to the PR, and please also change the status of this issue to
closed (duplicate).Please ask support questions on Drupal Answers.
Comment #2
drzraf commentedhopefully serious FLOSS projects my daily-use desktop rely on, do not close bugtrackers / ignore issue this way.
bug reportiers do not deserve 50 python lines to migrate their bug-reports automatically from d.o to github ?
Comment #3
greg.1.anderson commentedSorry, but issues are posted against Drush faster than maintainers can address them; there were 600+ unaddressed at the time of the migration. Sorry that your feature request was not reviewed and committed; sometimes, minor issues get missed due to time constraints..
If we were still reviewing patches on drupal.org, I would set this to "needs work", and say that Drush should abstract the notion of colored output so that we don't have console color constants scattered around the code. A PR that cleaned up the existing use of color and added color to other areas in Drush would probably be well received on GitHub.
Comment #4
greg.1.anderson commentedNote also that when I sent out this tweet, I got very little help in the queue.
Comment #4.0
greg.1.anderson commentedsyntax