[comp.windows.x] Selections and cut buffers

black@masscomp.UUCP (Sam Black) (05/10/89)

I'm trying to figure out how to use selections and cut buffers in xterm.
According to the man page, you should be able to set up something like:

XTerm*VT100.Translations:	#override\n\
	~Shift ~Meta <Btn2Up>:	insert-selection(PRIMARY, CUT_BUFFER0) \n\
	 Shift ~Meta <Btn2Up>:	insert-selection(SECONDARY, CUT_BUFFER1) \n\
	 Shift ~Meta <Btn3Down>:start-extend() \n\
	~Shift ~Meta <BtnUp>:	select-end(PRIMARY, CUT_BUFFER0) \n\
	 Shift ~Meta <BtnUp>:	select-end(SECONDARY, CUT_BUFFER1)

which "should" allow you to have multiple selections available for cut/paste.
However, the insert-selection always seems to paste the most recently defined
selection, be it PRIMARY or SECONDARY.  Does anyone out there know what's going
on?  Is there any way to do what I want?  Will Lance marry Jill?  Will Ollie
get accquitted?  Does anyone care?

		- sam black

--------------------------------------------------------------------------------
I'm pink, therefore I'm Spam.
		     ___________
		    /  ________/__	...!{decvax,uunet}!masscomp!black
		   /__/_______/  /	black@masscomp.com
	  Concurrent /__________/
	Computer Corporation
--------------------------------------------------------------------------------

swick@ATHENA.MIT.EDU (Ralph R. Swick) (05/10/89)

> Date: 9 May 89 21:00:05 GMT
> From: Sam Black <ukma!mailrus!ulowell!masscomp!black@ohio-state.arpa>
> ...
> According to the man page, you should be able to set up something like:
> ...
> which "should" allow you to have multiple selections available for cut/paste.

The man page didn't make clear that currently an individual xterm can
only _provide_ one selection at a time.  The example you extracted
works just fine for pasting multiple selections or for making the
(single) highlighted region one of the selections.

This is probably a mis-feature of the R3 implementation, but with
our current work queue it's unlikely to be fixed in the next release.
We'll fix the docs instead.