Re: [Bug: 21.4.17] Xemacs and Acroread lockup issue

Darin Perusich wrote: Yep; that comes under "cut" (or "kill", in Emacs terminology). Most of XEmacs' "deletion" operations (e.g. C-w, C-k) save the deleted text on the kill-ring (similar to a clipboard, but it keeps a history of previous values, not just the last value). The default setting of the interprogram-* variables has the effect of synchronising the kill-ring with the clipboard. Whenever you add something to the kill ring (which is usually whenever you delete anything more than a single character), it also gets stored on the clipboard. Whenever you paste something, anything that is on the clipboard gets pasted before what is on the kill-ring. This is fine on Windows, and isn't too bad on a typical Linux desktop system where the X server is running on the same system as the applications. But if you are using X over a network, or if there are any problems with clipboard handling (Motif bugs, broken clipboard managers), it's a bad idea. Clipboard problems when killing text can be eliminated by setting interprogram-cut-function to nil, so that kill operations don't update the clipboard. But if you do that, you'll also need to set interprogram-paste-function to nil, otherwise you'll end up pasting whatever happens to be on the clipboard rather than the last thing you killed (which isn't getting stored on the clipboard any more). -- Glynn Clements <glynn(a)gclements.plus.com&gt;