https://bugs.kde.org/show_bug.cgi?id=399473
Bug ID: 399473
Summary: [feature] proper exit after SIGHUP
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Session support
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
It happens that I run kdevelop on a remote X11 connection and forget to quit it
before moving to another terminal or suspending the system (= remote server
becoming unresponsive/unavailable but not exiting).
It would be useful in such situation if KDevelop triggered a proper exit in
response to a signal; traditionally that would be the hang-up signal (although
I'm not positive that this is still or ever was the signal sent by the X11
server when it's going down). Currently I have to use a signal to kill the
process, evidently, with the risk of losing the DU cache and recent changes to
the session and/or project settings.
Some might object that the user could have unsaved documents and should get a
chance to intervene. That argument is moot IMHO; when a hang-up is in progress
it is too late for that.
The proper exit I have in mind is one that does everything a normal exit does
except for saving new changes to files (except possibly to temporary files like
under some crash situations). In fact, no X11 activity should occur in case the
remote server has become unavailable.
--
You are receiving this mail because:
You are watching all bug changes.
