From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: getclip and cygutils and cygcheck
Date: Sat, 15 Jun 2013 19:36:00 -0000 [thread overview]
Message-ID: <51BCC258.3070304@towo.net> (raw)
In-Reply-To: <CAOh4nmkU4ydx1FTxcL11OV3sUG9Qdb1RnLjV-x7KwOVW34Kciw@mail.gmail.com>
Am 15.06.2013 05:15, schrieb Jeremy Hetzler:
> On Fri, Jun 14, 2013 at 5:15 AM, Corinna Vinschen wrote:
>
>> What's that size? I'm not aware of any size restriction in the current
>> /dev/clipboard code. Well, there's an allocation when writing to the
>> clipboard, but it's only restricted by the size of the largest available
>> memory block in the process VM, in theory.
> After some testing, the limit seems to be 64k. It only happens when
> reading data that was copied to the clipboard by a Windows program (in
> this case Excel).
This sounds pretty much like the same observation I made in
http://cygwin.com/ml/cygwin/2012-06/msg00521.html
At that time, however, the problem was finally fixed, so (not yet having
checked again, sorry) could the old problem have crept in again somehow?
------
Thomas
--
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
next prev parent reply other threads:[~2013-06-15 19:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 14:48 Nellis, Kenneth
2013-06-12 15:22 ` Nellis, Kenneth
2013-06-12 15:40 ` Corinna Vinschen
2013-06-12 17:57 ` Christopher Faylor
2013-06-12 19:53 ` Thomas Wolff
2013-06-13 9:56 ` Corinna Vinschen
2013-06-13 18:13 ` Jeremy Hetzler
2013-06-14 9:16 ` Corinna Vinschen
2013-06-15 3:15 ` Jeremy Hetzler
2013-06-15 3:36 ` Jeremy Hetzler
2013-06-15 17:45 ` Arthur Tu
2013-06-15 19:36 ` Thomas Wolff [this message]
2013-06-17 10:16 ` Corinna Vinschen
2013-06-17 13:13 ` Corinna Vinschen
2013-06-19 17:30 ` Corinna Vinschen
2013-06-19 17:35 ` Jeremy Hetzler
2013-06-19 17:45 ` Corinna Vinschen
2013-06-19 17:11 ` Ken Jackson
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=51BCC258.3070304@towo.net \
--to=towo@towo.net \
--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).