Re: --lock-flags now configurable, and some mu_argp reorg

[Alain Magloire]

> 
> > - mailutils allows you to write non-GPL programs, those programs
> 
> Excuse me, but I believe it does not. The COPYING file states that
> the whole suite is distributed under GPL, which means that any
> derivative work must be distributed under the same conditions as those
> set forth in the GPL.

Sam, mailutils/mailbox/*.[ch] is cover by LGPL but all the other programs
and supported mailutils/lib/* are GPL.  So programs are distributed
in terms of GPL and mu_argp_parse(), I beleive is only use in applications
not the core lib API.

> > - just because there are other mail and from and sieve utilities in
> >   the world, doesn't mean that I should have to rename the config
> >   files for mine as ~/.mu.???rc, IMHO. It is handy to isolate/group
> >   rcfiles sometimes, though, so now if ~/.mailutils is a directory,
> >   then that directory is searched for the rc files, instead of ~/.
> > 
> >   I can add back the .mu. prefix for config files if thats not
> >   sufficient, but I really like the directory of config files, an
> >   idea I shamelessly stole from mutt.
> 
> Sam, there was a good reason for renaming mailutils-specific configs.
> You will see it if you create a ~/.mailrc containing this:
> 
> set ask askcc append dot save crt hold
> set indentprefix="> "
> ignore Received Message-Id Resent-Message-Id Status Mail-From Return-Path Via
> set prompt="& "


Hoo... that is not good.  We should be able to understand the old format
".mailrc" if exist, use our own that have precedence.  Same like
vim; reads ~/.exrc or ~/.vimrc if exists, or bash etc ..
In any case coredump is not a good way to response to an error.

Of course IMHO.

> and then try to execute mailutils' mail utility. It simply won't
> work. So .mu prefixing is necessary. Of course, we may make "mail"
> an exception with its own config, but it will be clumsy and hard for
> people to remember.