x-selection-strict-motif-ownership is where I started with the OP on
comp.emacs.xemacs. It made no difference. BTW, I have it set to nil.
I just tried:
(setq interprogram-cut-function nil)
and it had no effect.
- vin
Glynn Clements <glynn.clements(a)virgin.net> writes:
Vin Shelton wrote:
> > Marco> I've seen some problems when I tried to do C-w on larger
> > Marco> selections but I never tried to figure out what's wrong:
> >
> > Marco> The above recipe on "XEmacs 21.4 (patch 5) "Civil
Service"
> > Marco> [Lucid] (sparc-sun-solaris2.8) of Tue Oct 23 2001 on jena"
> >
> > Marco> simply looks like it's hanging no spike in cpu or memory
> > Marco> consumtion but also no termination of the delete.
> >
> > Please attach your Installation file, or M-x describe-installation.
> >
> > It doesn't happen for me, and the main difference I see at the moment
> > is that everything I have has Mule. Is anybody seeing this in Mule
> > builds?
>
> Stephen, what is your value of zmacs-regions? If it's nil, you won't
> see this problem. As I noted earlier, this problem is also
> specific to X: I don't see it under either Window or xemacs -nw.
It might be worth checking whether it is affected by the setting of
interprogram-cut-function and/or x-selection-strict-motif-ownership.
--
Glynn Clements <glynn.clements(a)virgin.net>