https://bugs.kde.org/show_bug.cgi?id=356168
--- Comment #5 from [email protected] --- (In reply to Thomas Lübking from comment #4) > The kmail implementation looks "incomplete" (re-edit?), but, though > suboptimal for preserving the mail body in a conversation, the manual > process cannot be "prevented" anyway. You can re-edit a message in Kmail. When the "text editor™" is closed and the message is loaded into the composer, if you try to edit the message again, the "text editor™" is opened with the message. The same applies for conversations. When you click on the "Reply" button, the conversation is loaded into the "text editor™". Another video showing how to re-edit, and what happens if you try to close the composer while the "text editor™" is running: https://youtu.be/k3ytViakXMg > My position would be to improve the mail composer to lower the need to use > an external editor (if trojita would depend on KDE, I'd opt for simply using > a kate part) and iff we integrate external editors (to improve the > non-preventable manual process) to do it "better". I use vim and one of its advantages is the use of plugins to improve the user experience. Therefore, improving the mail composer would not be as close as using a "text editor™". Once you start using a "text editor™", going back to a simpler editor is quite difficult. I call this the "Vim Abstinence Syndrome" ;-) > Shortcomings in what I saw: > > - mail composer is editable while the ext. editor is up > -> what happens on concurrent input? merge? what if the merge fails, does > the user get a merge resolution request? ;-) > => lock the composer (ie. *hide* the body editor) When Kmail is configured to use a "text editor™", the composer is blocked until the "text editor™" is closed. The message "External editor was started" appears at the bottom of the composer. Thus, concurrent input is not possible. > - user must not forget to save in the external editor before closing it (no > idea how to fix that, but well, a user problem ;-) That's a user problem. Or a "text editor™" problem; it should warn the user when it is being closed. -- You are receiving this mail because: You are watching all bug changes.
