X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=DHQDwB7NG3QDthswJq8fjI+e1GIhetg3xpLiroj5wKZd0QrYTgfaT l8TrjkMgefzZ1jerPlPT/FOzZJU/aP3+8Qbs1qWpfBo9C+Bzzb/ehE1PPupjO7E4 ECGnEpMUh/xSI6CZQbHZSYpL3TMhl0Ypl7oVkQRG0Ers4bDkTScn5Y= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=c0TkA7YA/keM5X7b4NhQQcpzz6A=; b=M/q1IUlG+ZiwfRSo8zjs/s5OLrWg 2KBCJAochW8sPzG4mkI2NElr4oELK7UxNDoZCcodCAfzquMp1n5tJzDk8nme1k/a VQA/nziByFAzMSJNqYrlqlwXW5ZTpFzD8P3HczyBN7sb+g4AkDdV2byneAu9j004 h97Nb3fsmzr/4II= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.3.1 Date: Fri, 9 Aug 2013 09:54:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Redirecting cat and paste to file gives garbage Message-ID: <20130809075420.GA30689@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5203A1A3 DOT 30200 AT cs DOT utoronto DOT ca> <20130808153250 DOT GN16868 AT calimero DOT vinschen DOT de> <20130808154842 DOT GQ16868 AT calimero DOT vinschen DOT de> <5203C238 DOT 6010809 AT cs DOT utoronto DOT ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On Aug 9 05:53, Andy Koppe wrote: > On 8 August 2013 17:07, Ryan Johnson wrote: > > On 08/08/2013 11:48 AM, Corinna Vinschen wrote: > >> > >> On Aug 8 17:32, Corinna Vinschen wrote: > >>> > >>> On Aug 8 09:48, Ryan Johnson wrote: > >>>> > >>>> Hi all, > >>>> > >>>> (no, that's not a typo in the subject line) > >>>> > >>>> 64-bit install, bash inside mintty, all latest packages with the > >>>> cygwin1.dll snapshot shown below... > >>>> > >>>> # <<< --- begin STC --->>> > >>>> $ uname -a > >>>> CYGWIN_NT-6.1 ryan-laptop-v02 1.7.23s(0.268/5/3) 20130729 19:11:42 > >>>> x86_64 Cygwin > >>>> > >>>> $ echo "Reading" > /dev/clipboard > >>>> > >>>> # hit [shift]+[insert] to paste > >>>> # (hopefully 8 characters is not "too long" to paste into a TTY) > >>>> # then hit ^D to finish > >>>> $ cat > tmp.txt > >>>> > >>>> $ cat tmp.txt > >>>> Rg > >>>> eRaedaidnign > >>>> g > >>> > >>> The only idea I have is this. The clipboard data is stored as > >>> CF_UNICODETEXT and as the Cygwin-private CYGWIN_NATIVE_CLIPBOARD format. > >>> How's shift-insert implemented in mintty? If it reads the CF_UNICODETEXT > >>> part and sends it to the pty unchanged, that could explain > >>> this behaviour. > >> > >> The pty already gets 16 chars. And pasting the text into CMD or, FWIW, > >> any Windows console window works as expected. So this looks like a > >> mintty bug right now. > > > > That's what I thought at first, too, but it pastes fine directly into the > > terminal... and then I had a brain cramp and didn't add that to the STC: > > > > $ echo reading > /dev/clipboard > > # press [shift]+[insert] here... > > $ echo > > reading > > > > Still a mintty bug? > > Don't think so. Mintty has no idea what it's pasting to; it just > writes the clipboard content to the pty (which it obtains from > CF_UNICODETEXT and converts to the current charset). > > I couldn't reproduce the problem with 1.7.22, but I could with the > 20130729 snapshot. With 1.7.22, when you paste during the 'cat > >tmp.txt', the text is correctly echoed back to the terminal and put > into the file. With the snapshot, it looks like the actual input and > the echo both end up in the file. The snapshot date should have been a fairly good hint, but I missed it nevertheless. The problem is an accidental checkin which was reverted on 2013-07-31. Consequentially, if you would update to the 2013-07-31 snapshot, the problem should go away... with the tiny downside that we neglected to upload a 64 bit snapshot on 2013-07-31. Duh. I'm going to release 1.7.23 today anyway, so I'll not upload a new snapshot for now. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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