X-Recipient: archive-cygwin@delorie.com X-Original-To: cygwin@cygwin.com Delivered-To: cygwin@cygwin.com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 583D33858439 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Subject: Re: Incompatible clipboard format between 32bit and 64bit cygwin To: cygwin@cygwin.com References: <20210926103325.5c17eb11c3c8a56c377199a8@nifty.ne.jp> <584f536c-b108-b562-b940-798ec2847c68@maxrnd.com> <0b13b9ac-583f-ab72-4202-f8b187946d93@towo.net> <498f0cfb-c6c1-cb61-2e88-fcb9ce61f4d4@maxrnd.com> <731c8611-4ed2-29fd-0b9c-33e221d6451e@SystematicSw.ab.ca> From: Mark Geisert Message-ID: Date: Tue, 28 Sep 2021 10:11:37 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <731c8611-4ed2-29fd-0b9c-33e221d6451e@SystematicSw.ab.ca> X-Spam-Status: No, score=-4.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 18SHCacV023578 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 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple