On Mon, 30 Aug 2010, Timo Juhani Lindfors wrote:
Thomas Dickey <dic...@his.com> writes:
I do see a difference. It was actually copying to primary based on
this line in the default translations:
Hmm. I am not quite sure how to change the defaults without rebuilding
xterm but when "appres XTerm" shows
....
*VT100.font6: 10x20
XTerm*VT100.Translations: #override\n\
Shift Ctrl <KeyPress> v:insert-selection(CLIPBOARD)\n\
Shift<Btn1Down>:select-start()\n\
Shift<Btn1Motion>:select-extend()\n\
Shift Ctrl <KeyPress> c:select-end(CLIPBOARD)\n\
<BtnUp>:ignore() \n
*ptyInitialErase: true
....
steps 1 and 2 indeed seem to do what I asked. However, there's a side
effect: after that it seems that the terminal ignores all keyboard
input. This includes normal characters and also ctrl-shift-v that
would be needed in step 3.
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).
(There's also the issue that one can't move the mouse between steps 1
or 2 but let's not worry about that yet.)
yes... (because it would introduce mouse motion events). I suppose it
would help for this case to have an action that tells xterm to ignore
further select-extends, until a selection is started (to map the button-up
event to that).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org