public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /dev/clipboard corrupted
Date: Thu, 28 Jun 2012 08:04:00 -0000	[thread overview]
Message-ID: <CAHWeT-bDF+9-NH6FUP1f+v1W4o-_GgDF2kRy8PACjTqOWBRWug@mail.gmail.com> (raw)
In-Reply-To: <4FEB863A.7030108@towo.net>

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

  reply	other threads:[~2012-06-28  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 22:16 Thomas Wolff
2012-06-28  8:04 ` Andy Koppe [this message]
2012-06-28  8:21 ` Corinna Vinschen
2012-06-28 18:33   ` Thomas Wolff
2012-06-29  7:24     ` Corinna Vinschen
     [not found] <1286377403.634959.1340961856516.JavaMail.open-xchange@email.1und1.de>
2012-06-29  9:47 ` Thomas Wolff
2012-07-02 20:40   ` Corinna Vinschen

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=CAHWeT-bDF+9-NH6FUP1f+v1W4o-_GgDF2kRy8PACjTqOWBRWug@mail.gmail.com \
    --to=andy.koppe@gmail.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).