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

Darin> - <crtl-w> to kill the region Darin> at this point xemacs will not be responsive and you will Darin> need to kill the process. and Darin> Compiling in support for Motif. Darin> *WARNING* Many versions of Motif are buggy, requiring workarounds. Darin> You are likely to experience slow redisplay. Darin> You may need to install vendor patches to Motif. Darin> See PROBLEMS for more information. We're not kidding. Motif is definitely crash-prone and potentially slow, especially on Linux (both OSF Motif and Lesstif). But the commercial Motifs have had their share of issues too. Of course it's possible in any given case that it's an XEmacs bug, and we'll take a look at this one as best we can, but at the moment as far as I know we have no X-oriented developers using Motif as their primary platform, so debugging is likely to be slow. 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. However, changing any of these variables will most likely result in incorrect cut and paste behavior between applications. Let us know how it works for you. -- School of Systems and Information Engineering 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.