1 |
It boils down to underneath everything is Xlib and the guts of X. The |
2 |
guts of X have many ways to do the same thing and the result is QT, |
3 |
GTK, KDE, GNOME, etc all end up messing with a different piece of how |
4 |
X should handle cut/paste. As another post points out - there seems to |
5 |
be 2 different ways of doing cut/copy/paste. It seems that many like |
6 |
the second way - or just completely ignore "changing" how the second |
7 |
way operates. I would gamble you might have a couple of applications |
8 |
that specifically change how each of the cut/paste methods work |
9 |
because the programmer is a nazi and thinks only one way is good (for |
10 |
example maybe he hates using the "primary way" so he makes the "second |
11 |
way" fudge the "first way"). |
12 |
|
13 |
As an example, it looks like the Firefox/Mozilla people want to |
14 |
enforce the "first way". So people like me (who love highlighting and |
15 |
clicking) get pissed off because the behavior is changed in JUST |
16 |
firefox. It doesn't feel consistent. I can also see why someone would |
17 |
be a nazi (like the realplayer people are) for the "second way". Do |
18 |
you know how annoying it is to highlight something in a dtterm in |
19 |
Solaris and then you can't paste it into something else? For example, |
20 |
I highlight in firefox, but it doesn't paste in my xterm... and my |
21 |
xterm doesn't seem to like any combination of Ctrl-V, etc |
22 |
|
23 |
The thing is, mozilla/firefox are GTK apps. It could be that GTK just |
24 |
doesn't give a crap about cut/paste which leaves the programmer to do |
25 |
whatever he/she wants. Which resultes in randome GTK applications |
26 |
acting different. |
27 |
|
28 |
Yes, it is a bunch of BS and it is why many people just stick to KDE |
29 |
or GNOME... rejecting other software. However, it is this fully |
30 |
tweakable aspect of X11 that gives us the many different windows |
31 |
managers, applications, headaches, and flaming mailing lists. |
32 |
|
33 |
On Nov 16, 2007 8:12 AM, Crayon Shin Chan <crayon.shin.chan.uk@×××××.com> wrote: |
34 |
> On Friday 16 November 2007, Bryan Whitehead wrote: |
35 |
> > This is the default behavior of X. Highlighting IS copying to the |
36 |
> > clipboard. |
37 |
> |
38 |
> My point is that text which I did not *specifically* highlighted should |
39 |
> never be placed in the clipboard (whether primary/secondary/whatever). |
40 |
> Real life example: |
41 |
> |
42 |
> 1) in firefox/mozilla using CTRL-L will highlight the address url so you |
43 |
> can quickly replace it with something else, you can also use CTRL-V to |
44 |
> paste in something off the clipboard because firefox/mozilla does not |
45 |
> affect the clipboard when the address url is highlighted. |
46 |
> |
47 |
> 2) in Realplayer using CTRL-L will bring up a dialog where you can type in |
48 |
> a url, the current url is displayed in the dialog and is already |
49 |
> highlighted. However realplayer has also overwritten the clipboard with |
50 |
> the current url, which in 99.9999% of cases is NOT what a user wants, |
51 |
> because now I cannot paste in a new url without having to first delete |
52 |
> the current url, then go back and copy the new url and finally paste it |
53 |
> into realplayer. |
54 |
> |
55 |
> > This is just how X works. Getting around this is a |
56 |
> > hack in itself. |
57 |
> |
58 |
> But how is it that all KDE programs have "hacked" it so that it behaves |
59 |
> correctly (IMO), whereas some gtk based programs like realplayer are just |
60 |
> so clumsy (to put it charitably). |
61 |
> |
62 |
> -- |
63 |
> |
64 |
> Crayon |
65 |
> -- |
66 |
> gentoo-user@g.o mailing list |
67 |
> |
68 |
> |
69 |
-- |
70 |
gentoo-user@g.o mailing list |