In CSoar, if you do "matches production_name" it just gives you a short version listing the conditions of the production and how many matches there are for each condition. If you do "matches --wmes production_name" you get a very verbose output that includes all the WMEs included in every match and/or partial match of the production (it's when there are partial matches that things get extremely verbose).
However, in JSoar, you get the "--wmes" output even when you don't specify that option. There does not appear to be a way to get the "brief" version of the matches command output. This can be very inconvenient for debugging, because there is so much output.
The matches command has now been fully implemented as of commit e1d9e21. (As of this writing, this commit has not yet been pushed to github, but exists in SoarTech's internal repo.)
In CSoar, if you do "matches production_name" it just gives you a short version listing the conditions of the production and how many matches there are for each condition. If you do "matches --wmes production_name" you get a very verbose output that includes all the WMEs included in every match and/or partial match of the production (it's when there are partial matches that things get extremely verbose).
However, in JSoar, you get the "--wmes" output even when you don't specify that option. There does not appear to be a way to get the "brief" version of the matches command output. This can be very inconvenient for debugging, because there is so much output.