|
From: | Nathan Bailey |
Subject: | Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal) |
Date: | Fri, 06 Jan 2006 13:53:28 +1100 |
User-agent: | Thunderbird 1.6a1 (Macintosh/20060102) |
Using perl, it's relatively trivial to convert HTML, PDF or Word documents back to text, so the hierarchical defaults could support those, but for the most part, I'm prepared to view the actual attachment (except for HTML), so I haven't written that in.
The only thing that my module doesn't yet do to be a basic MUA is repl'y :-)Of course, it only implements a very small subset of MH functionality, but it's enough to access IMAP. And it doesn't do the fundamental (and key) operation of refile'ing between IMAP and disk-based folders. I also intend to make it exec normal MH commands if it determines the folder is a non-IMAP one.
Ken -- if you've got the different architectures on hand, I'd be interested in seeing them. I think that MH should, at the very least, support scan and show for IMAP.
re, N Ken Hornstein wrote:
If I had a need for IMAP support, I would sooner consider writing a FUSE module for an IMAP filesystem. It'd have more chance of working with scripts written around MH because non-MH commands would work. Short of a grab only mode in inc I'd be against cluttering all the nmh commands with IMAP details.See, it's this attitude that makes me say repeatedly, "If you want to do IMAP in nmh, just do it and commit it before anyone finds out". It's the only way it will happen; if people just _talk_ about it, all of the naysayers will start screaming and the interested party will go away, as it's happened a half-dozen times before. (I think I've seen 3-4 different architectures for doing IMAP in nmh, all completely different. Clearly people have very different ideas on how IMAP should work). --Ken _______________________________________________ Nmh-workers mailing list address@hidden http://lists.nongnu.org/mailman/listinfo/nmh-workers
[Prev in Thread] | Current Thread | [Next in Thread] |