After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 112635 - Confirmation dialog for closing terminal
Confirmation dialog for closing terminal
Status: RESOLVED DUPLICATE of bug 87771
Product: gnome-terminal
Classification: Core
Component: general
2.2.x
Other All
: Normal enhancement
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-05-09 13:41 UTC by Robin Green
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Robin Green 2003-05-09 13:41:09 UTC
Could we have a confirmation dialog when you try to close a gnome-terminal?
I accidentally closed a gnome-terminal window due to clicking close twice
on a window above it (I was confused about which window was on top of
which). This led to the closing of quite a few programs. Unlike (typically)
in Windows, the closing of a terminal window can be quite a MAJOR event,
especially if you run progs without using "nohup foo&", so I think it
should be subject to confirmation.

In fact, Windows and KDE both ask for confirmation (well, in KDE it's maybe
only if you have multiple tabs open, which is strange, but in Windows it's
if you have a running program other than a recognised shell, which is
sensible.)

If you make it confirmation for closing each tab, rather than each window,
that could be irritating. But on the other hand, to avoid being asked for
confirmation, users can quit text-mode programs cleanly and quit shells
using CTRL+D. Unless they've selected "run again after exit" in the
profile. (This could be mentioned in the confirmation dialog.)
Comment 1 Olav Vitters 2003-07-08 07:04:55 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 87771 ***