From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: /dev/clipboard sometimes fails to set CF_UNICODETEXT data.
Date: Tue, 5 Jul 2022 00:42:50 -0700 [thread overview]
Message-ID: <62975088-7bc3-7dde-d08c-3972126304f1@maxrnd.com> (raw)
In-Reply-To: <20220702122056.39a6c5e49c637d028694412e@nifty.ne.jp>
Hi Takashi,
Takashi Yano wrote:
> Hello,
>
> In one of my PCs,
> dd if=/dev/urandom count=10 | xxd > /dev/clipboard
> sometimes fails to set CF_UNICODETEXT data.
> As a result, pasting clipboard to notepad does not work.
>
> Even in the case, cygnativeformat data is set correctly.
> So, "cat /dev/clipboard" works.
>
> This problem depends on machine very much.
>
> My one PC with Xeon E3-1281 v3 CPU has a high probability of failure,
> however, another machine with Core i7-6700K CPU does not.
>
> I looked into this problem, and found OpenClipboard() for
> CF_UNICODETEXT fails. It seems that OpenClipboard() just
> after CloseClipboard() has high probability of failure.
>
> You can see the following test case immediately stops with error.
> Even with Core i7-6700K CPU machine above, the test case fails.
>
> #include <windows.h>
> #include <stdio.h>
>
> int main()
> {
> for (;;) {
> if (!OpenClipboard(0)) {
> printf("Open error.\n");
> break;
> }
> if (!EmptyClipboard()) {
> printf("Empty error.\n");
> break;
> }
> if (!CloseClipboard()) {
> printf("Cloes error.\n");
> break;
> }
> }
> return 0;
> }
>
> I also found the patch attached solves the issue.
>
> I would appreciate any suggestion.
Would be neet if this patch wasn't needed, but, oh well. My only comment on the
patch would be to possibly call the new wrapper function MyOpenClipboard, or
CygOpenClipboard, to help keep the name paired with CloseClipboard.
I suppose it might happen in the future that a faster processor will require the
loop count to be made larger. Once again, oh well.
My 2c (adjusted for inflation),
..mark
next prev parent reply other threads:[~2022-07-05 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 3:20 Takashi Yano
2022-07-05 7:42 ` Mark Geisert [this message]
2022-07-05 8:40 ` Takashi Yano
2022-07-05 11:42 ` Corinna Vinschen
2022-07-05 14:46 ` Andrey Repin
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=62975088-7bc3-7dde-d08c-3972126304f1@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).