[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Remove delay in `tset`
From: |
Bill Gray |
Subject: |
Re: Remove delay in `tset` |
Date: |
Sat, 9 Mar 2024 12:58:55 -0500 |
User-agent: |
Mozilla Thunderbird |
Hi Tim,
On 3/9/24 07:26, Tim Hutt wrote:
1. Some apps don't handle Ctrl-C properly. I think this is
understandable given that it is sent as a signal and signals are a
disaster from a programming UX point of view.
Where are you seeing this situation handled improperly?
I do know of one case where, if I Ctrl-C out of an ncurses program,
the terminal isn't completely reset. In xfce4-terminal, if my
program has turned mouse movement events on using CSI ?1003h [0], and I
Ctrl-C out, then moving the mouse over the terminal generates garbage.
In that case, it's to be expected; I'm the one who sent the control
code, not ncurses. ncurses does (in my experience) a complete job of
cleaning up anything it's reset.
Seems to me that if you're encountering cases where ncurses is not
resetting the screen correctly after Ctrl-C, then perhaps that ought to
be fixed, rather than relying on reset/clear/etc.
2. Sometimes apps have bugs and you have to kill them. They can't
reasonably do anything in that case.
This is the usual instance where I find myself applying reset/clear.
The programs involved are my own, which sadly means I must claim the
bugs as my own as well.
-- Bill
[0]
https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Any-event-tracking