Re: [Bug: 21.4.17] Xemacs and Acroread lockup issue
Stephen J. Turnbull wrote:
In the meantime, correct Motif selection/clipboard handling is very
complex, and many applications get it wrong (possibly including XEmacs
:-( but the guys who wrote the code worked very hard to get it right).
First, try setting `x-selection-strict-motif-ownership' to nil. Next,
look at the variables `interprogram-cut-function' and
`interprogram-paste-function'; perhaps setting one or both to nil will
give relief.
Personally, I'd suggest doing it the other way around.
Setting the interprogram-* variables to nil will eliminate clipboard
issues altogether for copy/paste within XEmacs. You can still
copy/paste between XEmacs and other applications using C-insert and
Sh-insert.
Having XEmacs' kill ring continuously synchronised with the "system"
clipboard is all well and good on Windows, where there is very little
overhead. On X, where clipboard handling involves multiple round-trips
to the X server, as well as potential interaction with clipboard
management utilities, it doesn't make sense, IMHO; it's far better to
keep internal and external operations distinct.
Setting x-selection-strict-motif-ownership to nil reduces the overhead
of copy/paste between XEmacs and other programs, but at the cost of
correctness. Essentially, pasting multiple items from XEmacs to
another application doesn't work; each paste operation pastes the
first thing that was put on the clipboard. To paste something new, you
have to make another application own the clipboard to force XEmacs to
reacquire ownership correctly.
--
Glynn Clements <glynn(a)gclements.plus.com>