Path: utzoo!attcan!uunet!husc6!ogccse!blake!uw-beaver!mit-eddie!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: xterm cut buffer
Message-ID: <8904272358.AA01826@expire.lcs.mit.edu>
Date: 27 Apr 89 23:58:24 GMT
References: <745@masscomp.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 21


    Using the R3 xterm, when you select text to be put into the cut buffer it
    gets highlighted.  Then if you just click the cut button, without selecting
    any text, the highlighted area is unhighlighted.  This makes sense, because
    xterm is no longer the owner of the cut buffer.  Nobody owns it any more.

You are confusing selections (a protocol term) and cut buffers.  When you
select text, xterm (by default) is both asserting ownership of a selection, and
storing the text in a cut buffer.  When you de-select, it disowns the
selection, but it does not clear the cut buffer.  When you then attempt to
paste, xterm first tries for a selection (but nobody has it), and then falls
back to the cut buffer.

If you don't like this default behavior, you can change the translations
for xterm, e.g. to only deal with selections.  [I'm not sure xterm provides
a way to clear a cut buffer.]

    Instead of just
    repainting the text to be highlighted, it repaints the whole screen.

Not as far as I know.