Re: [Mutt] #3323: Sending postponed messages doesn't save a copy in
#3323: Sending postponed messages doesn't save a copy in $record
-------------------------------+--------------------------------------------
Reporter: antonio@â | Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt | Version: 1.5.20
Resolution: invalid | Keywords:
-------------------------------+--------------------------------------------
Comment(by Derek Martin):
{{{
When I looked at this at first, I was inclined to agree with Aaron
that this is not valid, but now I'm almost (but not quite) convinced
that this should be reopened... It seems to me that there's an
argument for not storing the value of $record in postponed, and moving
the calculation of FCC until just before the message is actually sent
(i.e. after the user tells mutt to send the message). Suppose the
user postpones a message, and then changes various settings that
affect the FCC folder. Then the user resumes the message and sends
it. It will be saved in the wrong folder, and most likely the user
won't imagine that that would happen, essentially resulting in the
message being lost (at least until the user notices it was saved in
the wrong place, and also realizes that it was *not* saved in the
right place).
It may be that changing this behavior is hard... I haven't looked at
the code. But it seems like it at least ought to be open for
consideration. It's not clear that it's a bug (to me at least),
but it's also not clear that it isn't... I tend to think of UI design
decisions that result in the program behaving in ways that are both
undesirable, and that the user has no reasonable way to expect as
bugs, and I think this behavior may fall into that category.
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3323#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent