🚀 go-pugleaf

Hi.

    >    Date: 20 May 91 07:23:18 GMT
    >    From: amdahl!nsc!taux01!pilat!amir@ames.arpa  (Amir J. Katz (Xpert))
    >    Organization: Silvaco Israel Ltd.
    >    Sender: epoch-request@cs.uiuc.edu
    > 
    >    Following a discussion on the newsgroup, there is a workaround:
    > 
    >    - Before cutting something from an Epoch window, go to an xterm window
    >      and then select (e.g. cut) a single space: 
<...>
    >       Amir J. Katz, System Manager
<...>


Below is what I got some time ago, it seems to work ...

-- hws



Date: Thu, 6 Dec 90 13:41:04 -0800
From: beldar@mips.com (Gardner Cohen)
Cc: epoch@cs.uiuc.edu
Subject: epoch mouse cut -> X cut buffer

   I have the same effect here. It seems xterm has a special cut/paste
   logic that gives a nonempty selection on the xterm preference over
   the cut buffer.

Use the following XTerm resource to override this behavior:

! emacs only copies to cut buffer 0.  xterm by default 
! wants to paste from the PRIMARY selection
! make unshift middle be cut buffer 0, shift middle be PRIMARY
XTerm*VT100.Translations: #override \
	~Meta ~Shift <Btn2Up>: insert-selection(CUT_BUFFER0)\n\
	~Meta Shift <Btn2Up>: insert-selection(PRIMARY)


The Meta thing may not be necessary.  Note that the above causes R2
xterms to dump core, but works for R3 and R4.