Re: why does M-w (kill-ring-save) hurt so bad?

Jamie> Every time I type "M-w" to copy something to the kill ring, Jamie> xemacs stalls for 1 - 3 seconds. No kidding. Is this new to 21.4.8 or consistent across 21.4 releases for you? There was a fair amount of futzing with selection handling up to the release of 21.4.8, but as I recall it should not affect copying _to_ the clipboard from XEmacs. Jamie> At first this made me suspect that "copy the emacs kill to Jamie> the X clipboard" was on, but it doesn't appear to be. This stuff has been heavily hacked on. Ben changed it so that things always go through the clipboard by default, because that's the way it's done on Windows and Windows users lose badly if you don't. What is the value of `interprogram-cut-function' in your XEmacs? By default it's `own-clipboard', which does copy XEmacs kills to the X clipboard. And if `x-selection-strict-motif-ownership' is non-nil (which it is by default), you can get absurd amounts of X traffic from owning the clipboard. A >1 second delay sounds like you're getting hit by both. Can you get away with `interprogram-cut-function' nil? (Even if you need the clipboard _some_ of the time, you can get it only when you want it with `kill-primary-selection' and `copy-primary-selection', bound by default to the Cut and Copy, respectively, buttons on the toolbar.) -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.