On 31/12/2013 14:31, Franz Fehringer wrote: > I will not send you further personal email. > What i really meant was that i read in one of your announcements about > clipboard integration not fully working with the 64bit X server. > The reason why i came up with xwinclip is that i was under the (possibly > wrong) impression that xwinclip reappeared as a consequence of this > clipboard integration deficiency. > So the real question is: Is it true that clipboard integration is not > fully working with the 64bit X server and if so will this change in the > foreseeable future?
No, clipboard integration for 64-bit X server has been working since 1.14.1-2 (See [1]). [1] http://cygwin.com/ml/cygwin-xfree-announce/2013-06/msg00001.html > Am 31.12.2013 14:59, schrieb Jon TURNEY: >> On 31/12/2013 10:19, Franz Fehringer wrote: >> Firstly, do not send me personal email. >> >> Please read http://cygwin.com/problems.html#personal-email, particularly the >> section starting "Shouldn't I just send email to straight to a Cygwin >> developer or package maintainer?" >> >>> It seems xwinclip is still needed, what are the perspectives about this? >> >> I don't understand what you are trying to say here. >> >> If you are assuming that xwinclip is normally needed, because it is provided, >> then perhaps you should do some testing. It is not. >> >> See [1] and 'man xwinclip' for more details. >> >> To anticipate the next question: xwinclip is provided to assist in debugging >> clipboard integration problems, and because it is useful with the >> experimental >> XtoW window manager. >> >> If you are reporting a bug that xwinclip is needed when it shouldn't be, then >> more information is needed. >> >> [1] http://x.cygwin.com/docs/ug/using-clipboard-integration.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
