public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: Egmont Koblinger <egmont@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Data corruption when pasting large data to terminal
Date: Wed, 15 Feb 2012 16:10:40 -0800	[thread overview]
Message-ID: <20120216001040.GA21919@kroah.com> (raw)
In-Reply-To: <CAOULuObKZX_VER0ERPNBb0gS8GBQBHpJBHQcpJi2kNBBysL=2A@mail.gmail.com>

On Wed, Feb 15, 2012 at 06:58:12PM -0500, Parag Warudkar wrote:
> On Wed, Feb 15, 2012 at 1:50 PM, Egmont Koblinger <egmont@gmail.com> wrote:
> > Hi,
> >
> > Short summary:  When pasting large amount of data (>4kB) to terminals,
> > often the data gets mangled.
> >
> > How to reproduce:
> > Create a text file that contains this line about 100 times:
> > a=(123456789123456789123456789123456789123456789123456789123456789)
> > (also available at http://pastebin.com/LAH2bmaw for a while)
> > and then copy-paste its entire contents in one step into a "bash" or
> > "python" running in a graphical terminal.
> >
> 
> FWIW, this also works fine on cygwin / Windows 7.  No errors.
> 
> $ bash --version
> GNU bash, version 4.1.10(4)-release (i686-pc-cygwin)
> 
> Unsure what that means though - probably nothing!
> 
> Greg - when you said it works in vim - since of course vim isn't
> 'parsing' the input may be you did not see an error - or did you
> actually verify all 4KB somehow? ;)

I verified that the input actually matched the paste buffer.  It's
pretty trivial to do so.

Odds are emacs also does this correctly, anyone care to verify that?

thanks,

greg k-h

  reply	other threads:[~2012-02-16  0:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGWcZkJs2uQHM=7wmf1JOLmUeS3Mxo5L4arMuMQSez1mvJLKQA@mail.gmail.com>
2012-02-15 18:50 ` PROBLEM: Data corruption when pasting large data to terminal Egmont Koblinger
2012-02-15 23:30   ` Greg KH
2012-02-16  0:39     ` Egmont Koblinger
2012-02-16  0:54       ` Greg KH
2012-02-16  1:12         ` Egmont Koblinger
2012-02-17 19:28         ` Pavel Machek
2012-02-17 21:57           ` Bruno Prémont
2012-02-19 20:55             ` Egmont Koblinger
2012-02-19 21:14               ` Bruno Prémont
2012-02-19 21:35                 ` Alan Cox
2012-02-19 21:41                 ` Egmont Koblinger
2012-02-20 17:18                   ` Egmont Koblinger
2012-02-20 17:31                     ` Pavel Machek
2012-02-20 21:11                       ` Egmont Koblinger
2012-02-20 21:29                         ` Egmont Koblinger
2012-02-15 23:58   ` Parag Warudkar
2012-02-16  0:10     ` Greg KH [this message]
2012-02-16 11:42       ` Egmont Koblinger

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=20120216001040.GA21919@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=egmont@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.lkml@gmail.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