Path: utzoo!attcan!uunet!lll-winken!uwm.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!Mips.COM!beldar
From: beldar@Mips.COM (Gardner Cohen)
Newsgroups: comp.emacs
Subject: Re: x-store-cut-buffer doesn't work?
Message-ID: <39883@mips.mips.COM>
Date: 3 Jul 90 20:06:10 GMT
References: <4300079@m.cs.uiuc.edu> <18293@fs2.NISC.SRI.COM>
Sender: news@mips.COM
Reply-To: beldar@Mips.COM (Gardner Cohen)
Organization: Mips Computers, Inc.
Lines: 34

carroll@m.cs.uiuc.edu writes:

   You have to be careful. Under R4, most clients have moved to using
   selections instead of cut buffers. My impression from fiddling with
   xterm's (for instance) is that they will use the cut buffer only if
   there is no selection available. If there is, they'll use that
   instead of the cut buffer.

I mailed this to the original poster, and will offer it here in case
anyone else has the same problem.

Add the following to your xresources:

! emacs only copies to cut buffer 0.  xterm by default 
! wants to paste from the PRIMARY selection 
XTerm*VT100.Translations: #override ~Meta <Btn2Up>:
insert-selection(CUT_BUFFER0)

... to make R3 or R4 xterm paste from the cut buffer.  I think R3
xterm always copies to both cut buffer 0 and the primary selection.  I
haven't used R4 enough to determine its behavior; check the man page
for related translations.

R2 xterm appears to dump core when confronted with this translation,
so I use .Xdefaults-hostname to set this on machines I know have r3 or
later.  Your environment may vary.

Alternatively, the r4 client xcutsel allows you to copy back and forth
between cut buffer 0 and the primary selection.

Hope this helps.
--
Gardner Cohen     beldar@mips.com   {ames,decwrl,...}!mips!beldar (408)
524-8267