Re: mh strange behaviour

Hi Pierre-Jean,

>   Local-Mailbox : Your Username <[email protected]>

Thanks for reminder.  The 'Your Username' part is not supported yet,
but I'm going to implement that too.

> While calling an external program works well, a simple 'edit' now
> fails, if the 'Editor' entry of mh_profile contains options (ie, vim
> -c 'set ft=mail'). It was working well before, and it is still working
> well if the 'Editor' entry has no options (ie, a simple 'vim').

FWIW, that conforms with the behaviour of nmh whatnow utility.  However,
I agree that it can be a useful feature, so I pushed the fix.  Please pull.
Notice also that, albeit convenient, this functionality introduces a
certain ambiguity to the semantics of *-next entries in the profile.
Consider the following example:

editor: vi -i
vi-next: vi

The first "edit" command will invoke "vi -i", and all the subsequent
ones will invoke vi without additional options.  That's OK.  But what
if I want to provide a -next entry for the invocation of vi without
arguments?  There's no way of doing that, because the * in *-next is
replaced by the command name only.  I could implement (as extension)
somthing like "vi--i-next" to handle this case, but I haven't made my
mind yet.  Opinions?

> Localname, localdomain, and username are also given by the 'from'
> parameter of the smtp url that mailutils understands, aren't they?

Yes, you're right.

Regards,
Sergey