X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4FEB863A.7030108@towo.net> References: <4FEB863A DOT 7030108 AT towo DOT net> Date: Thu, 28 Jun 2012 09:03:41 +0100 Message-ID: Subject: Re: /dev/clipboard corrupted From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 27 June 2012 23:16, Thomas Wolff wrote: > If the clipboard contains large data, the contents retrieved from > /dev/clipboard gets corrupted. > I compared the following in a few cases: > * cat /dev/clipboard or cp /dev/clipboard (which are equal) > * mouse-paste into mintty, read with cat > * read /dev/clipboard within application > > and I found all three results to be different, the correct one sometimes > being cat /dev/clipboard but not always. > In today's case, the differences occured at byte 10240 and 65536 > respectively, thus 10K-1 bytes or 64K-1 bytes being equal. I don't know anything about that problem, but note that mintty accesses the clipboard directly via the Windows API, and that it converts both Windows line endings ("\r\n") and Unix line endings ("\n") to carriage returns ("\r"), because that's what the Enter key sends. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple