Xref: utzoo gnu.emacs:3870 comp.windows.x:27025 Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!bionet!agate!shelby!neon!lucid.com!jwz From: jwz@lucid.com (Jamie Zawinski) Newsgroups: gnu.emacs,comp.windows.x Subject: Re: X cutbuffer weirdness Message-ID: Date: 16 Sep 90 03:30:27 GMT References: Sender: jwz@lucid.com Organization: Lucid, Inc., Menlo Park, CA Lines: 16 In-reply-to: jwz@lucid.com's message of 15 Sep 90 07:19:25 GMT The strange interaction between Emacs, Xterm, and the cut buffers is because most Xterm clients use selections instead of (well, superceding) cut buffers. If there is a selection around, Xterms will use that instead of the cut buffer. Emacs doesn't know about selections, but you can convince Xterm to always use the cut buffer instead of selections by adding this to you .Xdefaults: ! emacs only copies to cut buffer 0. xterm by default ! wants to paste from the PRIMARY selection XTerm*VT100.Translations: #override ~Meta : insert-selection(CUT_BUFFER0) This works under R3, and probably R4, but not R2. Thanks to Thomas Narten for the prizewinning answer. He's going on to our bonus round where the scores can really change. -- Jamie