On Mon, Nov 17, 2014 at 11:32:59AM -0500, Mike O'Dell wrote:
Don't shoot, Robert, but
I think it's time MH took its turn in the refactory.
I like this thinking a lot. The biggest "selling" point of MH/nmh has been, in
my opinion, the storage architecture, which allowed mail files to be
manipulated by ordinary OS
commands, and allowed scripts to intermingle MH-specific commands with more
common commands. This, in turn, made it possible to write front-ends like xmh
and MH-E. I'd love to
extend this model by making MIME parts as manipulable as messages.
When I started writing my own Web-based front-end to an MH-based server, the
working title was AFMP ... archive/folder/message/part. That seemed like the
most useful way to
conceptualize the hierarchy of mail "things" that might interest a user.
I would, however, suggest forking off GOMH (good ole' MH) from MH++ if anyone
going to try this at home.
-pd
--
----
Peter Davis
The Tech Curmudgeon
www.techcurmudgeon.com
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers