octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Slow copy/paste feeding to IDE terminal


From: John Swensen
Subject: Re: Slow copy/paste feeding to IDE terminal
Date: Thu, 27 Sep 2012 10:16:51 -0400

On Thu, Sep 27, 2012 at 10:01 AM, John W. Eaton <address@hidden> wrote:
> On 26-Sep-2012, John Swensen wrote:
>
> | Does anyone know the root cause of how slow the characters appear when I 
> try to copy/paste into the IDE terminal (or double click on the history)?  
> I've tried to trace the code path that is execute on a copy/paste and can't 
> find anything specific about what might be causing the slow behavior.  I can 
> definitely type in the terminal window as fast as possible with not slow 
> effects, so I think it is isolated to behaviors that feed a string to the 
> terminal.  Another interesting behavior is with a recent patch I submitted.  
> The patch allows the user to select multiple lines in the history, 
> right-click and send them all to the terminal for execution.  The interesting 
> bit is that all but the final line of commands is sent to the terminal and 
> executed immediately, but the final line of the history has the characters 
> appear slowly.
> |
> | John S.
>
> There is a patch for readline here:
>
>   https://lists.gnu.org/archive/html/bug-readline/2012-06/msg00008.html
>
> jwe

So I have a hack that fixes this problem until this readline patch get
propagated.  The solution is to feed the string " \b", a space and
backspace character, to the terminal after any type of paste operation
to the QTerminal widget. This means that only these 2 characters are
subjected to the slow behavior. Are you OK with putting a band-aid in
there with a clear FIXME comment that this problem will go away after
future releases of readline?  It really is quite a pain to wait 5-10
seconds if I am trying to execute 10 lines of code from my history.
The only downside of this hack is that after the readline problem is
fixed, it will still be pasting two characters to the terminal after
each paste operation.

John S.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]