public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: L A Walsh <cygwin@tlinx.org>
Subject: Re: retry: Problem transfering X11 cut/copy buffer to windows and back
Date: Sat, 07 Sep 2019 17:27:00 -0000	[thread overview]
Message-ID: <c76ba87e-0bbb-52e1-88c7-226d63fc515d@dronecode.org.uk> (raw)
In-Reply-To: <5D633C75.5020204@tlinx.org>

On 26/08/2019 02:57, L A Walsh wrote:
> 
> Starting a few days ago, after an update to cygwin,
> I'm finding it impossible to transfer
> my xselection from cygwin X to any Win application or vice versa.

Are you using xorg-server 1.20.5-1 or later test release package?

I made some significant changes to the clipboard code in that, as noted 
in the announce  mail [1].

[1] https://cygwin.com/ml/cygwin-announce/2019-06/msg00009.html

> I've tried multpile Windows apps (Windows 7 SP1 x64)
> and multiple X apps and no go.
> 
> I first noticed it in gvim -- which I run on my linux box
> and display via 'X' locally.
> 
> The only thing I noticed w/X,u has been a checkmarked value about
> Clipboard may use primary selection (which is checked, though I tried both
> ways).
> 
> Having to write things out ot files is royal pain, so any ideas
> would be very appreciated.
-- 
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

  reply	other threads:[~2019-09-07 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  3:25 L A Walsh
2019-09-07 17:27 ` Jon Turney [this message]
2019-09-11  0:03   ` Jim Reisert AD1C
2019-09-11 17:11     ` Jon Turney
2019-09-11 22:54       ` Jim Reisert AD1C
2019-09-12  3:59       ` bzs

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=c76ba87e-0bbb-52e1-88c7-226d63fc515d@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /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).