public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: XFree86-xserv-4.3.0-38 test results
Date: Mon, 12 Jan 2004 17:44:00 -0000	[thread overview]
Message-ID: <4002DCD4.8060003@msu.edu> (raw)
In-Reply-To: <000b01c3d920$587e02e0$1e54cea7@andrew>

Andrew,

Andrew Braverman wrote:
>>[...]  For now, I would just drop the xhost command from
>>your startup file.
> 
> 
> No problem.  I can deal with it as long as you are aware of the issue.

Okay.  I think it needs to be fixed eventually so that the problem is 
not repeatedly reported.

>>>On a different note, I have noticed that the X clipboard
>>
>>will transfer to
>>
>>>windows as long as the data is highlighted.  Once the data
>>
>>is unhighlighted
>>
>>>(i.e. typing "clear") the text is still in the X buffer
>>
>>(middle button or
>>
>>>shift insert pastes correctly), but the windows clipboard is empty.
>>
>>That is an interesting point that I had thought of, but didn't really
>>want to think hard about :)  I spent about 12 hours coding this up...
>>everytime I thought I had it, I realized that more basic changes were
>>needed in the clipboard code.  Now I have it working, I believe.
> 
> 
> It seems to work now.  Thanks.

No problem.

>>I have made your request work only for the PRIMARY and CLIPBOARD
>>selections.  It won't matter if the X client still has data in the
>>SECONDARY selection, because we do not monitor that selection.  So,
>>don't complain if you can still paste in one or two X apps but not in
>>Win32 :)
> 
> 
> I try not to COMPLAIN about anything. :-)  Seriously, though - I do realize
> how much time and energy are put into this project by the few core people
> and though I will report issues I see or ask questions, I will never
> complain about what is or is not done.  You guys do too much work to deserve
> that.  One of these days, I will make enough time to make some contributions
> of my own - and then I MIGHT have a right to complain a little.  You guys
> have done a wonderful job, and as many have said before, we appreciate your
> work.  Thank you.

Sorry.  My "complain" should be read as more of a "I am already aware of 
this problem, so it doesn't have to be mentiond" and it was really 
written for other readers, not for you.  I don't think you are 
complaining :)  It is just that if others see this in the future, I 
don't want them saying "me too" if they notice this problem.

> OS: Windows XP
> 
> Language: English
> 
> Win32->X11 Copy and Paste: Worked
> 
> X11->Win32 Copy and Paste: Worked
> 
> Xdmcp: Did Not Try

Thanks for testing!

Harold


      reply	other threads:[~2004-01-12 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3FFD075A.8020404@msu.edu>
2004-01-08 15:16 ` Updated: XFree86-xserv-4.3.0-33 Andrew Braverman
2004-01-08 15:20   ` Harold L Hunt II
2004-01-08 19:48     ` Andrew Braverman
2004-01-10  6:43       ` Harold L Hunt II
2004-01-12 15:25         ` XFree86-xserv-4.3.0-38 test results Andrew Braverman
2004-01-12 17:44           ` Harold L Hunt II [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4002DCD4.8060003@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).