Lock out kmail when trying to delete text in a 25000 line email

ianseeks bingmybong at btinternet.com
Fri Sep 15 12:06:47 BST 2017

On Friday, 15 September 2017 10:39:42 BST René J.V. Bertin wrote:
> I cannot answer your question, but this seems like a good use scenario for having a way to use an external composer on a case-by-case basis, via a dedicated action ("reply using external composer" in KMail itself, or "edit in external composer/editor" in an embedded composer window).
I think i'd prefer that the composer was a separate thread/process so it could possibly be killed on its own. OR be able to start kmail fresh and not where it left off (like you can do with a browser when it crashes, you get the choice to start where you left off or a complete new session) 

> Alternatively, make the composer a kpart too and use a simple helper process, much like browsers like Chrome now use individual processes per page (tab, window - you can actually kill those using an internal task manager without losing your browsing session, very useful in this kind of situation when you realise the resources required for the operation you just triggered).
> R.

Qt: 5.9.1
KDE Frameworks: 5.37.0
KDE Plasma: 5.10.5
kwin 5.10.5
kmail2 5.6.1
akonadiserver 5.6.1
Kernel:  4.13.1-1-default
Nouveau:  1.0.15_1.2

More information about the kdepim-users mailing list