From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Incompatible clipboard format between 32bit and 64bit cygwin
Date: Tue, 28 Sep 2021 10:11:37 -0700 [thread overview]
Message-ID: <bfbeaaa5-48d0-d12e-4856-ffba44f07763@maxrnd.com> (raw)
In-Reply-To: <731c8611-4ed2-29fd-0b9c-33e221d6451e@SystematicSw.ab.ca>
Hi Brian,
Brian Inglis wrote:
> On 2021-09-27 22:49, Mark Geisert wrote:
>> 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 ;-).
>
> Would it perhaps make sense to include struct stat with appropriate entries rather
> than a couple of adhoc members unrelated to much else?
I'm not planning to include struct stat. If that much info was needed for the
original implementation back in 2012 it would have been added then. I just
observe that 'stat' and fstat() can show something useful with the feature. I
don't recall what other package or program had the requirement for the feature.
Cheers,
..mark
prev parent reply other threads:[~2021-09-28 17:11 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
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 [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=bfbeaaa5-48d0-d12e-4856-ffba44f07763@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).