https://bugs.kde.org/show_bug.cgi?id=356168
--- Comment #4 from Thomas Lübking <[email protected]> --- (In reply to Jan Kundrát from comment #3) > I also miss mi editor's spellchecker, sure. http://wiki.qt.io/Spell-Checking-with-Hunspell > However, there are special rules about how an e-mail message should look > like >From the description and video, this seeks to automate * launch "text editor™" * write mail in "text editor™" * copy text into mail composer * close "text editor™" * finally process mail in composer 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. 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". 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) - there's no real connection between the composer and the external editor window (what belongs to what) -> this is "fixable" on at least X11 (we turn the composer into a transient for the editor window or xembed the latter), but we'll need xlib/xcb code for this... - user must not forget to save in the external editor before closing it (no idea how to fix that, but well, a user problem ;-) -- You are receiving this mail because: You are watching all bug changes.
