You'll like this ;-) The reason people have trouble on X is the gross hack that someone used to make selections go away if their underlying buffer gets deleted... they try to retrieve the selection using the type _EMACS_INTERNAL, which used to just return a verbatim copy of whatever was in the specified selection. *HOWEVER*, I changed the code so it could have multiple selections of different types (like on Windows systems' clipboards, where an application can leave [for example] text and RTF, or a bmp, a jpeg and a png). This is useful for all sorts of reasons - for example, in Postscript mode, we could put the code on the clipboard as text and as a Postscript image; we could even delayed-render it (X always behaves this way) as all sorts of bitmap types, using ghostscript if it's installed. Before the change, _EMACS_INTERNAL was guaranteed to return a value from the local selection cache. Now, however, there's never anything of that type in any of the selections, so the code goes and asks the window system, which, unsurprisingly, screws things up good and proper. I'm working on a fix right at this moment, so those afflicted by this nonesense will soon be free of it. (Aargh. It's even worse than I could ever have possibly imagined. Someone hard-coded a call to the code in x-select.el into kill-buffer! This is just too gross.) Regards, Alastair. ____________________________________________________________ Alastair Houghton ajhoughton(a)lineone.net