David R Boldt wrote:
> try
>
> (setq x-selection-strict-motif-ownership nil)
worked like a charm!! thank you.
I also had the suggestion for
(setq-default interprogram-cut-function nil)
(setq-default interprogram-paste-function nil)
from Jeff, which also worked.
what are the pros or cons of using either of these solutions?
The interprogram-*-function approach is a fix;
x-selection-strict-motif-ownership is a workaround.
Setting interprogram-*-function "detaches" XEmacs' kill/yank
operations from the clipboard; C-w, M-w, C-y etc are then purely
internal operations. You can still copy data between XEmacs and other
applications using C-insert and Sh-insert (if your system has Copy and
Paste keys, you can use those as well).
Setting x-selection-strict-motif-ownership does what "C-h v" says:
*If true and XEmacs already owns the clipboard, don't own it again in the
Motif way. Owning the selection on the Motif way does a huge amount of
X protocol, and it makes killing text incredibly slow when using an
X terminal. However, when enabled Motif text fields don't bother to look up
the new value, and you can't Copy from a buffer, Paste into a text
field, then Copy something else from the buffer and paste it into the
text field; it pastes the first thing again.
This can be a nuisance if you want to copy from XEmacs to another X
application via the clipboard.
Basically, x-selection-strict-motif-ownership breaks clipboard
operation to make it quicker, while interprogram-*-function separates
internal cut/paste from inter-program cut/paste.
--
Glynn Clements <glynn.clements(a)virgin.net>