[Konsole-devel] Bug#40710: Konsole only handles CLIPBOARD, not PRIMARY
kenny at whitecape.org
Fri Apr 12 02:49:07 UTC 2002
<quote who="Stephan Binner">
> > selecting but with no explicit copy should only set PRIMARY, never CLIPBOARD
> Why? The only purpose to select something in a "read-only" widget is to bring
> it to the clipboard. It was changed to current state after several requests.
That's a good point. I hadn't thought of it that way, but it makes sense.
Having selection->CLIPBOARD automatically simply was not what I expected; if
I select KHTML text, which is read-only (I don't mean the form widgets),
then it only puts it in PRIMARY; if I do an explicit Copy it puts it in
Some people like to select text to point it out to someone with them, and
many people select text as they read along (it sounds weird, but I'm not
making it up.) I suspect they mostly do that in large documents, not in
their terminal, though.
Mostly I didn't realize it was copying to both, and was confused by the
inconsistency with KHTML. Feel free to leave it the way it is, it seems well
> > Selecting text in Konsole copies this text to CLIPBOARD, not PRIMARY - you
> > can verify this by running the 'xclipboard' program, which monitors
> > CLIPBOARD - selecting some text will cause it to appear in xclipboard.
> It copies it to CLIPBOARD _and_ PRIMARY.
> > - middle mouse button should paste PRIMARY, never CLIPBOARD
> It does, perhaps you were confused because you think it only wrote CLIPBOARD?
Yes, I was. Sorry about that.
Thanks for your time.
More information about the konsole-devel