[Konsole-devel] [Bug 97680] New: Protect shells from unintentional closing them or killing important jobs

[Frank Hellmuth]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=97680         
           Summary: Protect shells from unintentional closing them or
                    killing important jobs
           Product: konsole
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: konsole-devel kde org
        ReportedBy: fhellmuth yahoo de


Version:            (using KDE Devel)
Installed from:    Compiled sources

Sometimes you start a long time running process in a shell. You continue to work in other konsoles and after some time human beings getting tired... :( . It's easy to loose track of multiple tabs in several separate konsoles. So it would be nice to

1) have a reminder (besides that there are multiple konsoles open), when you close a konsole that there are still *running* jobs in a different tab (that should be easy to implement if there are still running childs of that shell) and present them to the user.

2) have the posibility to lock a console (from a maybe very tired) user, by locking the keyboard for that specific tab, to prevent users to give the wrong process a "Ctrl-C". That should also be not that hard to implement (maybe give the window additionally a "alarming" background colour).

A more sophisticated way could be to have the possibilty to detach a tab from a console to another specially protected one for "important jobs", with all the nice things you could do with this approach, like having a special alert if one of these processes end with exit status != 0, renicing these jobs automatically, etc...

You know these nights when you work hard all night just to get you thesis/talk/... done before deadline and then you kill accidentally your calculation job just 10 minutes before the 6 hour process would have finished... :(