#3799: mutt -H <file> should modify the draft <file>, not create a copy
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.5.24
Resolution: | Keywords:
---------------------+----------------------
Comment (by dgc):
I don't think we need to poll. A behavior change is disruptive and not
necessary, so let's just not do it.
I'm +1 to clarifying the documentation.
I'm +0 on implementing new behavior. The rest of this message assumes that
we want to do that.
Regardless of whether you're doing template or draft (in the senses
described), I don't think that mutt should ever delete the source file on
completion. This is typically a behavior that you want in scripts, and a
script can easily enough remove the draft/template if that's what you
want. Mutt should be safe here and leave any pre-existing draft/template.
(But exit status should indicate whether the message was sent.)
This aside, I think I like Cameron's suggestion: leave -H alone and
introduce boolean -E to make the file editable: "mutt -E -H draftfile".
This leaves just one option that uses a filename to specify a mail file
and allows another option to control semantics of that file.
A final possibility: augment -H so that e.g. "-H foo" exhibits current
behavior, while "-H :foo" or somesuch shows the new behavior. I don't like
this as much. It's a confusing overload, but it does avoid adding new
command-line switches.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3799#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
