>In not keeping with usual MH practice, don't provide >-nodryrun? It just seems too confusing, and if you get it >wrong there's no -undo.
Thre's a certain amount of logic to that, but because there's no undo someone one might want to set a default of -dryrun to prevent errors, and then explicitly do the irreversible operation when they know it's issue free? This could be done by aliasing sortm to 'sortm -dryrun !*' or some such, but generally defaults are in .mh_profile _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
