From kde-bugs-dist  Thu Mar 31 22:14:06 2016
From: via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date: Thu, 31 Mar 2016 22:14:06 +0000
To: kde-bugs-dist
Subject: [konsole] [Bug 361256] New: Close/exit konsole on bash crash/termination
Message-Id: <bug-361256-17878 () http ! bugs ! kde ! org/>
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=145946245002905

https://bugs.kde.org/show_bug.cgi?id=361256

            Bug ID: 361256
           Summary: Close/exit konsole on bash crash/termination
           Product: konsole
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: konsole-devel@kde.org
          Reporter: wlt@obsidian-studios.com

There are many times I want to end a bash terminal session without recording my
history. I use kill -9 $BASHPID to exit bash and not save my history. I do that
so often I have an alias for it, bye. Every time I do this on konsole, instead
of konsole closing/exiting, I get a message in red "Warning: Program
'/bin/bash' crashed."

Reproducible: Always

Steps to Reproduce:
1. Open konsole
2. kill -9 $BASHPID
3. manually close the konsole window

Actual Results:  
Once bash crashes ( is killed ) and I must manually close the konsole window.

Expected Results:  
Konsole would close/exit upon bash crash. That way when I do kill -9 $BASHPID,
it closes the window entirely. Which is what I want to happen in addition to
not saving history. I am done with that terminal window entirely.

There really is no benefit to keeping the window open after bash crashes. Maybe
for scrollback history, but in my case I specifically do not care about the
history. Thus not wanting bash to record it to file. There is nothing more that
can be done in that window. You cannot resume or restart the crashed/killed
bash session.

-- 
You are receiving this mail because:
You are watching all bug changes.