postpone: change recall/postpone logic for custom folders

Change `:recall -f` behavior so it remembers the source folder the
message is taken from and the further `:postpone` call can save it back
to that folder.

Change the `:recall` tab closing behavior, so it no longer asks if the
recalled message needs to be deleted. This is now done automatically.

Add an optional `-t <folder>` parameter to `:postpone`, so the message
can be saved in a different folder.

Change `:postpone` behavior, so it checks if the message was
force-recalled from a different folder, and then it saves the message
there.

The "breaking" change is made to the closing handler of the recalled
message tab. There was a confirmation dialog that asked if the recalled
message needs to be deleted. This is now removed and replaced with a
pretty simple logic: if the recalled message is either sent or
re-postponed - it is safe to delete the original. Otherwise (if the
recalled message editing is discarded, any other reasons?) the message
is left intact, there is no need to ask for deleting it. If the user
don't need that message - they can delete it manually.

Another "breaking" change to the same handler is that it always works
this way regardless of the curently selected folder. There was an `if`
that checked that, but as the recalled messages are now only deleted if
they are re-sent or re-postponed, it seems that there is no need to
check the current folder anymore.

Signed-off-by: Vitaly Ovchinnikov <v@postbox.nz>
Acked-by: Robin Jarry <robin@jarry.cc>

1 files changed, 17 insertions, 5 deletions

diff --git a/doc/aerc.1.scd b/doc/aerc.1.scd
index ecaedfd6..440cfc29 100644
--- a/doc/aerc.1.scd
+++ b/doc/aerc.1.scd
@@ -199,16 +199,21 @@ message list, the message in the message viewer, etc).
 
 *:recall* [*-f*] [*-e*|*-E*]
 	Opens the selected message for re-editing. Messages can only be
-	recalled from the postpone directory. The original message is deleted.
+	recalled from the postpone directory.
 
 	*-f*: Open the message for re-editing even if it is not in the postpone
-	directory. The original message will be deleted only if it is in the
-	postpone directory.
+	directory. Aerc remembers the folder, so the further *:postpone* call will
+	save the message back there.
 
 	*-e*: Forces *[compose].edit-headers* = _true_ for this message only.
 
 	*-E*: Forces *[compose].edit-headers* = _false_ for this message only.
 
+	Original recalled messages are deleted if they are sent or postponed again.
+	In both cases you have another copy of the message somewhere. Otherwise the
+	recalled message is left intact. This happens if the recalled message is
+	discarded after editing. It can be deleted with *:rm* if it is not needed.
+
 *:forward* [*-A*|*-F*] [*-T* _<template-file>_] [*-e*|*-E*] [_<address>_...]
 	Opens the composer to forward the selected message to another recipient.
 
@@ -619,9 +624,16 @@ message list, the message in the message viewer, etc).
 *:prev-field*
 	Cycles between input fields in the compose window.
 
-*:postpone*
+*:postpone* [*-t* _<folder>_]
 	Saves the current state of the message to the *postpone* folder (from
-	_accounts.conf_) for the current account.
+	_accounts.conf_) for the current account by default.
+
+	*-t*: Overrides the target folder for saving the message
+
+	If the message was force-recalled with *:recall -f* from a different folder,
+	the *:postpone* command will save it back to that folder instead of the
+	default *postpone* folder configured in settings. Use *-t* to override that
+	or use *:mv* to move the saved message to a different folder.
 
 *:save* [*-p*] _<path>_
 	Saves the selected message part to the specified path. If *-p* is selected,