I tracked what I think is a bug in mh "send" program's argument parsing.
This might be common for other mh programs as well, but I haven't looked.
Here is a description of the problem:
Invoking Mailutils send command direct from the command line with the
exact same arguments that mh-e invokes it with, and invoking it without
quoated arguments.
In mh-comp.el's mh-send-letter function definition, MH send is called like:
(mh-exec-cmd-daemon mh-send-prog nil "-nodraftfolder" "-noverbose"
mh-send-args file-name)
All arguments have double quotes around them. The one with double
quotes, gave me the same error message as when invoked from within mh-e.
----------------
$ send "-nodraftfolder" "-noverbose" "-msgid "
"/home/henman/mail/drafts/1894"
send: invalid option -- m
error here with $? == 64.
----------------
$ send -nodraftfolder -noverbose -msgid
/home/henman/mail/drafts/1894
$
success here with $? == 0
Help. I tried going through send, but am not familiar with the argument
parsing at all.
I think that the programs should be able to handle quoted arguments.
Please look into it.
Thanks,
Darel Henman
_______________________________________________
Bug-mailutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-mailutils
