Hi,
the issues should be fixed in SVN 386.
When large value are printed then the computation of the output as well
as the printout itself can be interrupted (two ^C within 500 ms).
There is still some latency after the ^Cs because some internal functions
are not interruptible, but it is much smaller than before.
/// Jürgen
On 07/22/2014 09:28 PM, David Lamkins wrote:
Good to hear that a solution is in sight. :)
On Tue, Jul 22, 2014 at 12:04 PM, Juergen Sauermann
<juergen.sauerm...@t-online.de <mailto:juergen.sauerm...@t-online.de>>
wrote:
Hi David,
thank you very much. I read the paragraph below several times.
Unfortunately
the behavior of readline is somewhat different. The problem seemed
to be that
signal handling is "too transparent" in that it ignores settings
made in the signal
handler.
But I am on the way towards a solution. The first ingredient was
Blakes recommendation
to bind ^C. That was correct, except that it didn't work. It
worked for ^A, ^B, etc but
not for ^C. The missing piece was to entirely hide ^C's special
role from readline
before calling readline(). After that ^C could be bound like any
other ^something.
I am currently running a number of tests with this and I am hoping
that I can commit
the solution tomorrow. That should include your ^C comments and
also Blake's printout
issues.
/// Jürgen
