From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Incompatible clipboard format between 32bit and 64bit cygwin
Date: Mon, 27 Sep 2021 21:49:27 -0700 [thread overview]
Message-ID: <498f0cfb-c6c1-cb61-2e88-fcb9ce61f4d4@maxrnd.com> (raw)
In-Reply-To: <dd433ab8-ca9b-d6e8-3dce-c69a4dc9c593@towo.net>
Hi Thomas,
Thomas Wolff wrote:
>
> Am 26.09.2021 um 20:37 schrieb Thomas Wolff:
>>
>> Am 26.09.2021 um 11:50 schrieb Mark Geisert:
>>> Hi Takashi,
>>>
>>> Takashi Yano via Cygwin wrote:
>>>> I noticed that cygwin clipboard is not compatible
>>>> between 32bit and 64bit cygwin.
>>>>
>>>> If I run 'echo AAAAAAAA > /dev/clipboard' in 32bit cygwin,
>>>> and run 'cat /dev/clipboard' in 64bit cygwin, this result in
>>>> cat: /dev/clipboard: Bad address
>>>>
>>>> This is because the structure
>>>> typedef struct
>>>> {
>>>> timestruc_t timestamp;
>>>> size_t len;
>>>> char data[1];
>>>> } cygcb_t;
>>>> defined in fhandler_clipboard.cc has different size.
>>>>
>>>> Is this the known issue?
>>>
>>> I doubt anybody has ever tried what you did.
>> I have and it failed; I just didn't find it important enough to report it
>> here... Thanks for the plan to fix it.
>>
>>> I have been testing getclip and putclip between 32- and 64-bit environments,
>>> but neglected to test Cygwin-internal clipboard format that prepends cygcb_t to
>>> the user-supplied data.
> As we're at it, what's the purpose of a cygwin-internal clipboard format at all?
> Copy/paste between 32bit/64bit mintty works; mintty uses Windows CF_UNICODETEXT
> clipboard format.
The cygwin-internal clipboard format records a timestamp and content length when
Cygwin (or putclip) updates the clipboard contents. This allows 'stat' and
fstat() to show something sensible for /dev/clipboard. The latter feature went
into Cygwin 1.7.13.
Other than that, not much difference to CF_UNICODETEXT ;-).
..mark
next prev parent reply other threads:[~2021-09-28 4:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 1:33 Takashi Yano
2021-09-26 9:50 ` Mark Geisert
2021-09-26 18:37 ` Thomas Wolff
2021-09-26 18:41 ` Thomas Wolff
2021-09-26 19:09 ` Lee
2021-09-26 20:46 ` Brian Inglis
2021-09-28 4:49 ` Mark Geisert [this message]
2021-09-28 5:22 ` Brian Inglis
2021-09-28 6:19 ` Takashi Yano
2021-09-28 6:46 ` Brian Inglis
2021-09-28 8:13 ` Takashi Yano
2021-09-28 17:11 ` Mark Geisert
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=498f0cfb-c6c1-cb61-2e88-fcb9ce61f4d4@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@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).