Don't ask for compontent sources in fc

Often you'll know the machine name of something you want to export, so you can do fc %:%stuff%

Which still works just fine. We are just talking about "fc" without arguments here.

My own opinion is that on my sites, where I have a ton of features and components, the output of "fc" to just show everything is worthless. I'm never going to use it. I'd *always* filter it.

What I like about the prompting is that it quickly shows me which components I am using on a particular site. My sites have lots of non-core feature components, so it's a good reminder for me and saves me from typing out some of the longer component names.

I don't see it as a wart. Nobody is forcing you to use "fc" without arguments. You can still use it the way you want it with arguments. You can still use "fc %" to list everything for scripting. Just because most unix tools don't have interaction doesn't mean that all interaction is bad. It's taking a case that is ambiguous (no arguments) and prompting you for more information. "drush pmi" isn't a good example because there is nothing else for it to do other than show everything...there isn't anything you would ever prompt for. I still use "drush cc" prompting myself sometimes.

Just saying: different people have different opinions on this.

If all drush fc did was print out the component types and then exit, that'd be better off than printing EVERYTHING.
I think the numbered list isn't ideal, but its still more useful than the behavior of that patch before my change.

Sure, rewrite my part as drush fcl and make it mirror pml, I'll review that patch. But I don't memorize component names, and neither do the site builders I know that consider the prompt-then-list their favorite part of this feature.

+++ b/features.drush.inc
@@ -174,21 +180,30 @@ function drush_features_list() {
+  foreach (module_implements('features_api') as $module) {
+    $components = module_invoke($module, 'features_api');
+    drupal_alter('features_api', $components);
+    foreach ($components as $source => $info) {
+      $rows[] = array($info['name'], $source, $module);
+    }
+  }

use features_get_components

However, I don't think another command is needed. If they want all, they can do drush fc *, right? drush choice seems fine here.

We should document that it's drush fc %.
Chatted with moshe about drush_choice, and he's planning on using it heavily for a bunch of new drush features, and doesn't understand the aversion here.

> That's where I started, but I wanted to get the defining module, and that's the only way to do it currently.

Sounds like altering features_get_component to add a 'module' key would be useful.

While drush is a command line tool, drupallers been encouraging everyone to use it so changing things to be more usable doesn't seem bad.