[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Fwd: [Konsole-devel] clipboard behaviour
From:       Waldo Bastian <bastian () kde ! org>
Date:       2002-06-30 0:24:24
[Download RAW message or body]

Originally sent to konsole-devel, resent here for discussion. See the second 
forwarded message for a description of the current konsole copy&paste 
behaviour. For those not aware, we have two clipboards in KDE 3.x, the 
"selection-clipboard" which is copied to whenever you select something with 
the mouse and which can be pasted from with MMB, and the "ctrl-c/ctrl-v 
clipboard" which is copied to by selecting text and then pressing ctrl-c (or 
Edit->Copy) and pasted from by pressing ctrl-v (or Edit->Paste).

Konsole can not use ctrl-c or ctrl-v for anything because it needs to pass 
these keys to the applicatin running in konsole, e.g. ctrl-c is normally used 
to interrupt program execution.

Cheers,
Waldo

----------  Forwarded Message  ----------

Subject: [Konsole-devel] clipboard behaviour
Date: Friday 28 June 2002 12:33 pm
From: Waldo Bastian <bastian@kde.org>
To: konsole-devel@kde.org

I have come to the conclusion that the current clipboard behaviour of konsole
is broken. It might be ok if you look at konsole in isolation but
desktop-wide it causes inconsistency which IMO outweighs any benefits.
So I would like to remove the "automatically copy to clipboard" feature and
add a "Copy" action instead.
Cheers,
Waldo
----------  Forwarded Message  ----------

> > Yes, unfortunate we can't bind anything to ctrl-c/ctrl-v in konsole. We
> > get quite some bugreports about that actually. We also get quite a few
> > reports that ctrl-s causes konsole to freeze.
>
> could you not at the very least implement right click>copy/paste?

We have right click->paste.
We don't have richt click->copy because the idea was that if you select
something in konsole you most certainly will want to copy it to the
clipboard, so that is done automatically (so it gets copied to _both_
clipboards.) Since it is done automatically you don't need an explicit copy
function.
I'm wondering whether this has been a good decission though for several
reasons:
a) It makes assumptions about the user's intention
b) it breaks the clipboard model that ctrl-c copies to the clipboard and
selecting copies to the selection-clipboard.
c) users from a non-unix background search for "copy" and can't find it.
So this could very well contribute to the overall perception that "the
clipboard is broken", it's very hard to tell without detailed feedback from
people what annoys them about the current clipboard behaviour.
--
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com
_______________________________________________
konsole-devel mailing list
konsole-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/konsole-devel

-------------------------------------------------------

-- 
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]