I'm often asking myself "which modules are enabled in this site, anyway?" which of course leads me to pm-list, which I often run with --pipe, especially if I want to copy the list into some other document, which leads to manually removing the core modules. The --package filter is not convenient for this, so I added --contrib and --core options to pm-list. Problem solved.

n.b. --core could be removed, as it can already be done with an appropriate --package line, but --core is a bit more convenient.

CommentFileSizeAuthor
#4 pm-list-no-core.patch1.67 KBgreg.1.anderson
pm-list-contrib.patch1.67 KBgreg.1.anderson

Comments

moshe weitzman’s picture

moshe weitzman commented

Hmmm. We discussed this at #440962: a way to list enabled modules so that this output can be fed to a disable command - like in drush_mm module but never did add this option. I'm ambivalent on it. I do think that people expect it.

We should call them 'core' and 'no-core' since custom (i.e. site specific) modules would be listed in -- contrib.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Needs work
moshe weitzman’s picture

moshe weitzman commented
Assigned: Unassigned » greg.1.anderson
greg.1.anderson’s picture

greg.1.anderson commented
Status: Needs work » Needs review
StatusFileSize
new pm-list-no-core.patch1.67 KB

Here is the same thing with --no-core instead of --contrib.

moshe weitzman’s picture

moshe weitzman commented
Status: Needs review » Reviewed & tested by the community

comment needs updating: "// filter out core if --contrib specified". otherwise, rtbc

greg.1.anderson’s picture

greg.1.anderson commented
Status: Reviewed & tested by the community » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.