🚀 go-pugleaf

>>>>> On 13 Feb 91 14:04:10 GMT, smartin@Canada.lsil.com (Stephen Martin) said:

Stephen> I seem to have no problem cutting text out of an xterm and pasting it into
Stephen> epoch but when i try to go the other way it doesn't work.  Is there something
Stephen> i can configure to do this?

I have been having the same trouble, but a quick hack/fix that works
is to make sure no xterm owns the selection. ie. Highlight some text
in an xterm window, then do a mouse-button-1, which will de-select the
text. Now if you do a epoch region selection, the cut/paste will work
fine.

I belive the problem relates to epoch (emacs also too), not being able
saving the cut test in the primary cut buffer, if it still owned by
some other client.

Anthony
--
Anthony Mutiso (anthony@cs.ualberta.ca)                Life-motto: Logic Rules.

The problem is that Epoch uses cut buffers, and xterms like
selections. Here is something that can make things work a little
better.
-------
Here is a nice little hack to make life easier to cut & paste between
epoch and xterms or other Toolkit-based applications. Just before cutting
text into the cut buffer, clear the current selection, so that when you paste
in  a xterm afterwards, you will really paste the epoch text, no an old
selection hiding somewhere...

Here is the patch to src/x11fns.c:
avahi$ diff -c x11fns.c.orig x11fns.c
*** x11fns.c.orig       Wed Jul 18 11:06:01 1990
- --- x11fns.c    Wed Jul 18 11:09:35 1990
***************
*** 93,98 ****
- --- 93,99 ----
        check_xterm ();

        BLOCK_INPUT ();
+       XSetSelectionOwner(XD_display, XA_PRIMARY, None, CurrentTime);
        XStoreBytes (XD_display, XSTRING (string)->data,
                     XSTRING (string)->size);
        UNBLOCK_INPUT ();

(hack found by Arnaud Le Hors, lehors@mirsa.inria.fr, Koala Project)

-- 
Alan M. Carroll                "I hate shopping with the reality-impaired"
Epoch Development Team                 - Susan
CS Grad / U of Ill @ Urbana    ...{ucbvax,pur-ee,convex}!cs.uiuc.edu!carroll

	It's possible to hack around this problem using resources.  I have the
following settings in my .xrdb:

XTerm*VT100.translations:#override \n\
	<Btn2Up>: insert-selection(CUT_BUFFER0, PRIMARY)
*Text.translations:#override \n\
	<Btn2Down>: insert-selection(CUT_BUFFER0, PRIMARY)

	The root of the problem is that emacs and epoch put cut text into only
CUT_BUFFER0.  Xterm, but default, checks PRIMARY first, and then uses
CUT_BUFFER0 only if PRIMARY is empty.  If you've selected some text in
an xterm window, and then subsequently select epoch text, the xterm will
paste from the original xterm selection in PRIMARY.

	The second resource setting makes this apply to text widgets as well
(for xrn, for example).  I haven't noticed any side-effects from making
this change.  Do be careful, however, to use ".translations" rather than
"*translations".  If you use a *, the translation will also be in effect
in the scrollbar.  This causes xterm to crash.

		Gill Derge
		derge@crd.ge.com