Well, then I will fork the xwinclip development. That's the greatness of
open source.
I think that seamless integration with windows is very important.
And a Windows user never expects to lose the clipboard contents when he
selects text with the mouse.
Thanks for all.
Good bye.
Howdy Harold, you took the words right out of my mouth (well, maybe they
were a bit kinder than I'd have been!):
Subject: Re: xwinclip patch
...
Not all applications used the CLIPBOARD atom... a lot of them still only
use XA_PRIMARY. Dropping support for XA_PRIMARY is a HUGE reduction
Excellent.
[EMAIL PROTECTED] wrote:
Well, then I will fork the xwinclip development. That's the greatness of
open source.
I think that seamless integration with windows is very important.
And a Windows user never expects to lose the clipboard contents when he
selects text with the mouse.
Thanks
Nope, you really didn't read the mailing list.
Not all applications used the CLIPBOARD atom... a lot of them still only
use XA_PRIMARY. Dropping support for XA_PRIMARY is a HUGE reduction in
the feature set of xwinclip and it will not be accepted by users.
Harold
[EMAIL PROTECTED] wrote:
Howdy Harold, you took the words right out of my mouth (well, maybe they
were a bit kinder than I'd have been!):
Subject: Re: xwinclip patch
...
Not all applications used the CLIPBOARD atom... a lot of them still only
use XA_PRIMARY. Dropping support for XA_PRIMARY is a HUGE reduction
What I'm requesting is so simple as this:
--- xwinclip.c.orig 2003-01-13 02:27:22.0 +0100
+++ xwinclip.c 2003-06-04 10:09:18.0 +0200
@@ -362,15 +362,6 @@
exit (1);
}
- /* Assert ownership of PRIMARY */
- iReturn = XSetSelectionOwner (pDisplay, XA_PRIMARY,
-
