Joel wrote:
> According to mhstore(1)'s man page, setting nmh-storage in my
> .mh_profile will cause mhstore to put MIME attachments into the
> directory given as the value of nmh-storage instead of the current
> directory. It seems that this does not work in conjunction with the
> -auto option for mhstore. When -auto is given, the attachments are
> written to the current directory, regardless.
>
> Is this intentional? a bug? It would be nice if it were possible to
> save attachments with their given names, but to a preset directory.
It looks intentional:
/*
* Check for the directory in which to
* store any contents.
*/
if (autosw)
dir = getcpy (cwd);
else if ((cp = context_find (nmhstorage)) && *cp)
dir = getcpy (cp);
else
dir = getcpy (cwd);
That's in store_all_messages () in mhstoresbr.c. I don't
know what the motivation was. According to the mhstore
man page, -auto is ignored under some conditions, and
"it is recommended that you do NOT put the -auto switch
in your .mh_profile." So I don't know why it's favored
over nmh-storage. Just a guess, but maybe nmh-storage
was added later and this approach minimized its impact.
David
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Nmh-workers mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/nmh-workers
