Use wildcard to enable/disable modules/themes

And the patch...

Attached an improved patch, thanks to code review from @psynaptic and @snufkin :)

Thanks for the reviews, @greg.1.anderson can you elaborate on how you think * at the end is confusing and ideas on making it more general purpose?

Thanks for the comments, I see what you mean - I can't recall ever wishing I was able to enable/disable modules using some sort of *foo* criteria (maybe some people do and as you rightly point out it could be a time waster for someone) however within 2 mins of installing drush and using it to dl views and context I was looking for an option such as 'drush en views* context*'

I guess it's partly because when you download views you get not only views but views_ui and views_export that I wanted some easy way to switch them all on without having to name the sub modules explicitly.

I agree on the point about documentation so in the attached patch I've added some lines and examples to hook_drush_help().

Do you think that is sufficient or is there more I could do on documentation?

Good thinking Moshe, I'll have a look through the commands and identify which would benefit from this.

Thanks @greg.1.anderson - I've been rummaging through drush code looking at these commands and so far it seems to me that they fall into two distinct types, commands that operate on the project release information (i.e. the 'main' module like views or context etc) and commands that can take (sometimes optional) a space separated list of module/theme names to operate on. I think it's these latter commands only which might benefit from this feature.

I've been through the following commands, I tried to follow them through to the functions they are calling in Drupal and to identify how they are working and whether this feature is appropriate or even needed...

pm-disable (dis) - so this works with the patch on comment 3, although drush already adds all the dependent modules to the list of modules it will disable so assuming you have views, views_ui and views_export installed issuing:

drush pm-disable views

produces

The following projects will be disabled: views, views_export, views_ui

pm-download (dl) - I don't think anything is needed here, all sub modules are downloaded when a main module is downloaded
pm-enable (en) - works with the patch on comment 3
pm-info - I think this command would benefit from the feature, I'll work on a revised patch
pm-list (sm) - nothing needed here, the command lists all sub modules anyway
pm-refresh (rf) - doesn't take any arguments, nothing needed here
pm-releases - I haven't thoroughly followed this command through but from testing it appears to work on project release info so passing in views_ui understandably returns "No information available."
pm-uninstall - not sure about this one, I need to dig deeper but it dependent modules are uninstalled by default by Drupal? With that in mind I don't think adding this feature makes sense for this command?
pm-update (up) - not needed, like pm-releases pm-update works on the main project info only
pm-updatecode (upc) - same as pm-update

So in summary I think pm-info appears to be the only additional candidate for this feature, I'll dig deeper into pm-uninstall and see what I can find.

As ever thoughts, comments and corrections appreciated ;o)

I've pulled out the code that expands the project names into it's own function so that it can be called from wherever and I've added the feature to the pm-info command as well.

Hi Moshe,

In the attached patch I've added an explanation and example in README.txt and also added to the 'arguments' array as suggested.

Hi Moshe,

Okay, the attached patch has the changes you mentioned.

That's great, thanks Moshe.