aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Gattozzi <mgattozzi@gmail.com>2020-01-03 10:35:12 -0500
committerMichael Gattozzi <mgattozzi@gmail.com>2020-01-03 10:43:34 -0500
commit81643fdcb0e6578f8c35e99579a2d0010d2eac8b (patch)
tree1fa8540cc4ee4165f934f8579959977b643dee3c
parenta33eac7f22abfdad430a3431ff3521ec9cde9dba (diff)
Create 'Create a panic handler for ticket tui'
-rw-r--r--.dev-suite/ticket/open/create-a-panic-handler-for-ticket-tui.toml17
1 files changed, 17 insertions, 0 deletions
diff --git a/.dev-suite/ticket/open/create-a-panic-handler-for-ticket-tui.toml b/.dev-suite/ticket/open/create-a-panic-handler-for-ticket-tui.toml
new file mode 100644
index 0000000..7b61c45
--- /dev/null
+++ b/.dev-suite/ticket/open/create-a-panic-handler-for-ticket-tui.toml
@@ -0,0 +1,17 @@
+title = 'Create a panic handler for ticket tui'
+status = 'Open'
+id = '9b344c00-2e3d-11ea-bc2d-b4e1317c6ecc'
+assignees = [[
+ '64c00ccc-761e-4484-86ac-904e461bb300',
+ 'Michael Gattozzi',
+]]
+description = '''
+When the ticket tui has a panic it garbles up the terminal and leaves it in an
+awful state. This is because it never sets the terminal back to it's previous
+state like it can when it fails gracefully. When the tui is run it should have
+a custom panic handler to reset the terminal to it's proper state, then continue
+with it's normal unwinding behavior.
+'''
+version = 'V1'
+
+[comments]