On Mon, 30 Aug 2010, Thomas Dickey wrote:
On Mon, 30 Aug 2010, Timo Juhani Lindfors wrote:
Thomas Dickey <dic...@his.com> writes:
I saw something like that, the first time I tried the script, but am
unsure where the problem lies. But then I ran a few more times
without encountering the bug (puzzled).
If it's more/less reproducible, I might be able to see something with
a debug-trace (unless the problem lies in the X libraries).
I see it quite often but not always :-)
The attached xterm.xtrace.bz2 shows how the terminal works for a while
but then stops responding. When it stopped responding I typed
"terminal is not responding" or something like that so that you can
find it from the trace (if you convert the keycodes back to ascii...).
thanks - I'm closing out #262 now, and it seems this bug-report will
keep me busy for a while...
I think it's likely that the unprocessed KeyRelease events are confusing
the X library. Adding ignore's for those seems to improve it:
*VT100*translations: #override \n\
Shift Ctrl <KeyPress> v:insert-selection(CLIPBOARD)\n\
Shift Ctrl <KeyRelease> v:ignore() \n\
Shift<Btn1Down>:select-start()\n\
Shift<Btn1Motion>:select-extend()\n\
Shift Ctrl <KeyPress> c:select-end(CLIPBOARD)\n\
Shift Ctrl <KeyRelease> c:ignore() \n\
<BtnUp>:ignore() \n
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100902041243.c44...@mail101.his.com
