From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Make native clipboard layout same for 32- and 64-bit
Date: Mon, 11 Oct 2021 08:11:24 -0400 [thread overview]
Message-ID: <ee8b46bd-f8f4-85da-be25-233c3cb60c71@cornell.edu> (raw)
In-Reply-To: <6de24f8c-bd21-cd4f-18ff-ece3fef85b89@maxrnd.com>
On 10/11/2021 2:13 AM, Mark Geisert wrote:
> It's just that after submitting the patch I realized that, if we really are
> going to support both Cygwin archs (x86_64 and i686), there is still the issue
> of different cygcb_t layouts between Cygwin versions being ignored.
>
> Specifically, the fhandler_clipboard::fstat routine can't tell which Cygwin
> environment has set the clipboard contents. My original patch takes care of
> 32-bit and 64-bit, providing both are running Cygwin >= 3.3.0 (presumably).
> What if it was a different version (pre 3.3.0) that set the contents?
I wonder if this is worth the trouble. Right now we have a problem in which
data written to /dev/clipboard in one arch can't be read in the other arch. The
fix will appear in Cygwin 3.3.0. Do we really have to try to make the fix apply
retroactively in case the user updates one arch but not the other?
Ken
next prev parent reply other threads:[~2021-10-11 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 5:22 Mark Geisert
2021-10-07 5:56 ` Mark Geisert
2021-10-08 9:52 ` Takashi Yano
2021-10-09 14:19 ` Ken Brown
2021-10-09 14:29 ` Jon Turney
2021-10-09 14:43 ` Ken Brown
2021-10-11 6:13 ` Mark Geisert
2021-10-11 12:11 ` Ken Brown [this message]
2021-10-22 15:11 ` Corinna Vinschen
2021-10-23 5:35 ` Mark Geisert
2021-10-23 20:32 ` Ken Brown
2021-10-23 21:53 ` Mark Geisert
2021-10-23 23:58 ` Takashi Yano
2021-10-25 8:28 ` Corinna Vinschen
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=ee8b46bd-f8f4-85da-be25-233c3cb60c71@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-patches@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).