[1208] in Release_Engineering
cut buffer vs. selections problems -- emacs vs. xterm
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Tue Jun 13 00:50:15 1989
Date: Tue, 13 Jun 89 00:50:02 -0400
From: Jonathan I. Kamens <jik@ATHENA.MIT.EDU>
To: vs-testers@ATHENA.MIT.EDU, rt-testers@ATHENA.MIT.EDU,
Unless we are planning on installing the new version of emacs that
Rob has been working on in the end-of-summer release, a very large
number of people is going to be very upset by the breakage which makes
it virtually impossable to paste things from emacs into an xterm window
reliably.
There is, however, a simple solution to this problem, and I propose
that it should be heavily documented in release notes and OLC stock
answers, and even possibly get hacked into our xterm sources until
emacs gets fixed.
The following translation table, when added to a person's X
resources, will make xterm/emacs cut-and-paste work properly in both
directions. I believe it will make it work all the time. It would be
relatively simple to modify the sources to xterm to make this a
default change to xterm.
XTerm*VT100.translations: #override\n\
~Meta<Btn2Up>:insert-selection(CUT_BUFFER0, PRIMARY)
Comments? (as if I have to ask :-)
jik
