When running under mh-e, I set the MHCONTEXT environment variable to
/dev/null. This prevents my mh-e context from confusing my command line
context.
With 1.1 this breaks things. With the default dot locking, this causes
lkopen_dot() to call lockit() which tries to mkstemp() a file in /dev
which
Paul Fox <[EMAIL PROTECTED]> wrote:
> > > > mailutils-mh is clearly not a mature project yet, [but] given that it
> > > > rides on top on GNU mailutils once it fully works it should provide
> > > > lots of functionality (POP, IMAP, etc).
> ...
> > there are still a few gaps in mailutils-mh co
> > > mailutils-mh is clearly not a mature project yet, [but] given that it
> > > rides on top on GNU mailutils once it fully works it should provide
> > > lots of functionality (POP, IMAP, etc).
...
> there are still a few gaps in mailutils-mh compared to nmh. But it's a
> fast moving targe
> I was wondering exactly the same; nmh versus a new, clean, code base.
> IIRC the recent announcement of a mailutils release said their MH
> implementation was happily being used by MH-E now.
>
> Cheers,
>
>
> Ralph.
A clean code base would be nice. Much of nmh dates back to the original
MH
Ralph Corderoy <[EMAIL PROTECTED]> wrote:
> Hi Peter,
>
> > mailutils-mh is clearly not a mature project yet, since given that it
> > rides on top on GNU mailutils once it fully works it should provide
> > lots of functionality (POP, IMAP, etc).
> >
> > This is not meant to be flamebait, so plea
Hi Peter,
> mailutils-mh is clearly not a mature project yet, since given that it
> rides on top on GNU mailutils once it fully works it should provide
> lots of functionality (POP, IMAP, etc).
>
> This is not meant to be flamebait, so please don't see it as such.
> I'm just wondering about the
I wrote:
> mailutils-mh is clearly not a mature project yet, since given that it
^
I meant to write "but" here. I hate it when that happens, but
apparently not enough to proofread my posts.
> rides on top on GNU mailutils once it fully work
> Glenn Burkhardt <[EMAIL PROTECTED]> wrote:
>
> > RC2 is seriously broken. You should pull a current CVS copy from
> > Savannah.
>
> I just tried that because I need the sequence fix on mh RH 9 system.
> But I'm not sure of the procedure for building from a CVS copy.
>
> Configure dies with:
>
