Michael Parker <[EMAIL PROTECTED]> writes: > Now you're adding in a whole other subsystem. Using this logic, it is > pretty easy to argue that everything should be in one executable, and > not split out. A little cross use is allowed. Here is my proposed > set of commands and their arguments:
> [...usages removed...] > sa-filter > sa-report > sa-learn (maybe sa-bayes) > sa-update > sa-history/sa-awl (maybe sa-whitelist) > sa-lint Hmmm... my thinking is that we have several basic actions people perform. - filtering and removal of markup - learning/forgetting - reporting/revoking - plugin-specific stuff that cannot be generalized I'd strongly favor move the basic learn functionality (learn, forget) into a single command regardless of the learning subsystem and the plugin-specific stuff like bayes, whitelist, and history into plugin-specific commands. I think 3.2 is perhaps the right place to do a larger restructuring than what is in 3.1. Daniel -- Daniel Quinlan http://www.pathname.com/~quinlan/
