From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18710 invoked by alias); 1 Sep 2017 14:03:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18700 invoked by uid 89); 1 Sep 2017 14:03:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=slip, wheel, forefront, H*r:bizsmtp X-HELO: h1.cmg1.smtp.forpsi.com Received: from h1.cmg1.smtp.forpsi.com (HELO h1.cmg1.smtp.forpsi.com) (81.2.195.162) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Sep 2017 14:03:24 +0000 Received: from [172.16.42.4] ([193.165.117.170]) by cmg1.smtp.forpsi.com with bizsmtp id 4E3M1w00B3gfz7l01E3NNl; Fri, 01 Sep 2017 16:03:22 +0200 Subject: Re: problem with paste-from-clipboard To: cygwin@cygwin.com References: <7250c40b-32a6-8000-6808-ac432fd72fc4@redhat.com> <5919e0cc.f3149d0a.5c156.0ea9@mx.google.com> From: Ladislav DANKO Message-ID: <9ee775c2-80dd-fe2e-2bc1-fd6f017ef52c@1ac0.net> Date: Fri, 01 Sep 2017 14:03:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00008.txt.bz2 is there any update on this please? On 15.05.2017 20:21, Eric Blake wrote: > On 05/15/2017 12:09 PM, Steven Penny wrote: >> On Sat, 13 May 2017 15:11:00, Eric Blake wrote: >>> You're making it sound like I'm actively trying to hurt you. Rather, it's a case where it is a problem that doesn't affect me personally, and I have >>> limited enough spare time as it is, so I haven't yet tried to reproduce things to see if I can isolate what behavior changed. >>> >>> I would love help solving the issue. Absent that help, you'll just have to wait for me to have time. >> >> But I have helped - in the very post of mine you just quoted, I put this link: >> >> http://cygwin.com/ml/cygwin/2017-04/msg00176.html >> >> that post of mine contains not only the commit in question, but even potentially the file in question and even possibly the section of the file in >> question. You never even responded to that post. > > Probably because I did not even see the post at the time. (While I try to keep up with Cygwin email, I also get hundreds of other mails per day, and when > Cygwin is limited to my free time, sometimes things slip through the cracks). In life, and therefore in open source, it is often that the squeaky wheel > gets the grease; if something isn't getting the attention you think it deserves, it is not bad to ping the thread to bring it back to the forefront. > > Thanks for the ping. I've now replied to that thread to ask upstream bash for help in deciphering if Chet, who wrote the code, might be aware of why it is > breaking things. > > That said, I still hope to get a closer look at it myself when I have a nice chunk of time; but the trick is still getting that nice chunk of time. > -- 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