bugGNU Octave - Bugs: bug #37450, Slow paste behavior for GUI...

 
 

bug #37450: Slow paste behavior for GUI terminal

Submitted by:  John Swensen <jpswensen>
Submitted on:  Thu 27 Sep 2012 07:21:33 PM UTC  
 
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: Performance
Status: Wont FixAssigned to: None
Originator Name: John SwensenOpen/Closed: Closed
Release: devOperating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Fri 28 Sep 2012 04:18:19 PM UTC, comment #5:

I don't think it is worth trying to fix this problem in Octave.

Put pressure on your distro to fix the bug in their readline package, and put pressure on Chet to make a bug-fixing release of readline. That will fix the problem for everyone, not just Octave users.

John W. Eaton <jwe>
Project Administrator
Thu 27 Sep 2012 08:31:50 PM UTC, comment #4:

I am not even going to bother with this. It seems like way more work than it is worth. You can go ahead and mark this as rejected/closed because I don't plan on working on it. I have a workaround and there are far more important things to be done than make a workaround for bugs in other libraries.

John Swensen <jpswensen>
Thu 27 Sep 2012 08:29:05 PM UTC, comment #3:

> Is it sufficient to have the autoconf macro test for a version
> number?


We normally test for features, not for versions. We have very few
tests for versions in autoconf.ac

> I still don't quite get how to check for the bug programatically.


I haven't tried to understand this carefully, but from my reading of
Chet's analysis of the bug, it should be possible to send events to
readline in the right way to trigger this bug and check if the hook
has been run or not.

If this is bugging you so much, you could just use readline 6.1. I
wasn't even aware of this bug because I am using Debian stable.

Jordi GutiƩrrez Hermoso <jordigh>
Project Administrator
Thu 27 Sep 2012 08:14:57 PM UTC, comment #2:

Is it sufficient to have the autoconf macro test for a version number? I still don't quite get how to check for the bug programatically. It seems that I could just check for anything after Readline 6.1. The fix is in their repository and an official patch alongside the 6.2 tarball on their source distribution server, but there is not release of 6.2.x or an indication of when that might occur.

So, (1) what is the proper way to do this test and (2) can you make an autoconf macro that is equivalent to a code snippet? I found some AC_LANG_SOURCE sections in the existing m4 directory, but am not sure if this is the right mechanism.

John Swensen <jpswensen>
Thu 27 Sep 2012 07:33:15 PM UTC, comment #1:

The solution to work around this sort of thing is to write an autoconf macro to test for the bug in readline and to use this macro to decide to implement the workaround or not.

Also, death to copy-paste code, even if it's a comment. Especially if it's a comment. I don't like having to go dig through this stuff later in the future and find the 3 different locations where I have to make the exact same change.

Jordi GutiƩrrez Hermoso <jordigh>
Project Administrator
Thu 27 Sep 2012 07:21:33 PM UTC, original submission:

There is currently a bug in GNU Readline that causes the terminal behavior of the GUI to be slow when sending text to the terminal. common occurrences of this is pasting to the terminal and executing history items. See https://mailman.cae.wisc.edu/pipermail/octave-maintainers/2012-September/030316.html where jwe pointed out the GNU Readline message board discussion about the bug.

Because I don't know when this bug will get fixed in their sources and propagated to various Linux distributions, I proposed the following patch to solve the problem. The basis of the patch is to send an additional string to the terminal that consists of a space and a backspace. This makes it so that every operation that sends text to the terminal in bulk with have a delay that is 0.1 seconds times two (the number of characters in the last string). Currently the delay would be 0.1 seconds time however many characters are in the last line of text sent to the terminal.

John Swensen <jpswensen>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #26661:  terminal_pasteslow.diff added by jpswensen (4KiB - text/x-patch)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by jwe (Posted a comment)
  • -unavailable- added by jordigh (Posted a comment)
  • -unavailable- added by jpswensen (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 28 Sep 2012 04:18:19 PM UTCjweStatusIn Progress=>Wont Fix
      Open/ClosedOpen=>Closed
    Thu 27 Sep 2012 08:29:05 PM UTCjordighStatusNone=>In Progress
    Thu 27 Sep 2012 07:27:43 PM UTCjpswensenAttached File-=>Added terminal_pasteslow.diff, #26661

    Back to the top


    Powered by Savane 3.1-cleanup1