🚀 go-pugleaf

Relay-Version: VMS News - V5.9C 19/12/89 VAX/VMS V5.3; site vax1.cc.lehigh.edu
Path: vax1.cc.lehigh.edu!vax1.cc.lehigh.edu!netnews.upenn.edu!rutgers!tut.cis.ohio-state.edu!isa.de!schwarze
Newsgroups: gnu.emacs.bug
Subject: Cut Buffers Problem
Message-ID: <9010181728.AA11946@isaak.isa.de>
From: schwarze@isa.de (Jochen Schwarze)
Date: 18 Oct 90 17:28:05 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Approved: bug-gnu-emacs@prep.ai.mit.edu
Lines: 21

The function x-store-cut-buffer from x11fns.c stores the text using
XStoreBytes(). If the current selection is owned by an xterm, the
selection owner will *not* be changed and the text yanked in xterm
with the middle button will not be the one that was just stored in
emacs. A simple, if somewhat non-conforming solution, is to put the
call 
    
        XSetSelectionOwner(XXdisplay, XA_PRIMARY, None, CurrentTime);

after XStoreBytes(). The selection owner will be cleared, in which
case an xterm will get the cut buffer directly, without asking the
selection owner. A better solution would be if emacs explicitly
requested the selection ownership and replied to SelectionRequest
events.  (I'm not too familiar with selections but as I see it that's
the way it should be done.)

-- 

Jochen Schwarze                     Domain: schwarze@isa.de
ISA GmbH, Stuttgart, West Germany   UUCP:   schwarze@isaak.uucp
                                    Bang:   ...!uunet!unido!isaak!schwarze