[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal)
From: |
mlh |
Subject: |
Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal) |
Date: |
Wed, 4 Jan 2006 10:36:57 +1100 |
User-agent: |
Mutt/1.4.2.1i |
On Wed, Jan 04, 2006 at 12:56:23AM +1100, Nathan Bailey wrote:
> Of course, the alternative is to write nmh in perl (or python, or ruby,
> ...). This has the benefit of reusing a whole bunch of code that is
> heavily used and maintained (for reading/writing email) and adding only
> the mh-specific bits on top. It also solves the problem of repl filters
> extensions -- if it's in perl, the repl filter can be arbitrarily complex.
Yeah re-use would be the way to go, surely.
The interpreter way has been done, or at least started. There are
python and perl libs for dealing with MH and IMAP mail.
Another re-use way would be to just borrow great swathes of
code from say, mutt or sylpheed.
This would also have the advantage of excising the ancient low-level
stdio intrusive code and other anachronisms.
Command line mutt anyone?
Matt
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Oliver Kiddle, 2006/01/03
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Joel Reicher, 2006/01/05
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Nathan Bailey, 2006/01/05
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Joel Reicher, 2006/01/05
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Joel Reicher, 2006/01/06
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Lyndon Nerenberg, 2006/01/06
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Ken Hornstein, 2006/01/06
- Re: [Nmh-workers] exciting new stuff for 2.0 (IMAP proposal), Joel Reicher, 2006/01/06