Re: Hydrant(mailutils's MUA) ideas

[Alain Magloire]

> > 
> > It was for me, but there was talk about scheme, python etc ..
> 
> I think that most of the layout and stuff could be exported to scheme
> trivially and without loss.  The underlying infrastructure I want to
> be C++.

OK.

> > > > Can I have write permission to the repository since it Hydrant will
> > > > not be included in mailutils.
> > > 
> > > Sure, I'll sort that out tonight.  I've been getting more annoyed with
> > > mutt recently.
> > 
> > Thanks.
> 
> Fini.

# cvs -d :pserver:address@hidden:/home/cvs co hydrant
cvs server: Updating hydrant
cvs server: failed to create lock directory in repository `/home/cvs/hydrant': 
Permission denied
cvs server: failed to obtain dir lock in repository `/home/cvs/hydrant'
cvs [server aborted]: read lock failed - giving up
# cvs -d :pserver:address@hidden:/cvs co hydrant
cvs server: Updating hydrant
cvs server: failed to create lock directory in repository `/cvs/hydrant': 
Permission denied
cvs server: failed to obtain dir lock in repository `/cvs/hydrant'
cvs [server aborted]: read lock failed - giving up

Can not try other directory because I forgot my subversion passwd ... sigh ....

> > > > Things are a little sketchy and I'm not in to writin docs 8(
> > > 
> > > Just create a notes file and jot stuff down.  There's no point in
> > > writing the docs for this until something's started to be written.
> > 
> > OK.
> 
> Just create NOTES in doc/

Will do once I have cvs access.

> > hmm ... that it is something I did not approach at all in mailutils
> > encryption, PGP, signatures etc ... I suspect it will possible to
> > added cleanly whithout shaking the foundations too much.
> 
> I think in many ways mailutils shouldn't have those.  signatures and
> other hooks are simply part of the message body normally, and PGP just
> needs to act on individual MIME objects which are already exported to
> the app.

Noted.

> > The real(visible) change is in memory management, where it will
> > be required that you xx_destroy() any object you xx_create ()
> > or xxx_get_yy ().
> 
> Ah, even more reason to have c++ bindings.  =)

nice 8)
Looking at it now, things could have been so much elegant in C++.