Re: name of the draft file in mh-comp.el

Olivier Lecarme <ol <at> i3s.unice.fr> wrote:

> When you make a forward, mh-forward, which is located in mh-comp.el,
> wants to create a file called draft, and complains if it already exists.
> A colleague of mine, who uses Sylpheed in parallel with mh-e, encounters
> this problem, since Sylpheed uses a folder called draft.
> 
> This is the unfrequent case of a name wired in the function (line 682
> sqq). Could it be made a customizable variable? Despite the comment in
> this line, the MH forw command does not have this problem, or at least
> it works even if a directory called draft exists.

Olivier,

Could you please submit a bug at http://mh-e.sourceforge.net/ where we
can discuss this?

The "draft" filename appears to be hard-coded in mh-read-draft as well.
There is a mh-new-draft-name function which seems like it could be
modified to handle a customization variable for the draft filename if
you're not using the Draft-Folder facility.

While I agree it would be nice to be able to change the name of the
draft file, we may not be able to do anything about this because I think
"draft" is hard-coded in MH. Since nmh offers arguments to set the name
of the draft in most commands, we might be OK there; however, we might
have compatibility issues with MH. Hopefully, I'm wrong .

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click