Do you think there is a way to configure that? Perhaps disable the
double-thing when in Emacs mode? The reason is that in Emacs mode you
already have to press C-c twice to send a sinvlde C-c to the underlying
process. That means that in order to interrupt right now I need to press it
4 times within 500 ms, which is very difficult.

Regards,
Elias


On 3 August 2014 00:27, Juergen Sauermann <juergen.sauerm...@t-online.de>
wrote:

>  Hi Blake,
>
> good. The double ^C is on purpose to avoid accidentally hitting ^C.
>
> Its actually two ^C within 500 ms.
>
> /// Jürgen
>
>
>
>
> On 08/02/2014 05:40 PM, Blake McBride wrote:
>
> Dear Juergen,
>
>  It prints immediately.  Great!!!
>
>  Last thing, if I could just ^C out of the middle of printing ⍳100000
> but I could ^C^C out!
> (I understand this may be a readline issue that'll have to wait.)
>
>  Thanks!
>
>  Blake
>
>
>
> On Sat, Aug 2, 2014 at 10:25 AM, Juergen Sauermann <
> juergen.sauerm...@t-online.de> wrote:
>
>>  Hi Blake,
>>
>> I did some rework of the print functions for APL values.
>> Some were not suited for values with many columns.
>> That should work better now. SVN 413.
>>
>> /// Jürgen
>>
>>
>>
>> On 08/01/2014 06:30 PM, Blake McBride wrote:
>>
>>  On Mon, Jul 21, 2014 at 5:33 AM, Juergen Sauermann <
>> juergen.sauerm...@t-online.de> wrote:
>>
>>>  Hi Blake,
>>>
>>> unfortunately the rules for APL output are such that you cannot "print
>>> as you go".
>>>
>>
>>
>>  Try ⍳100000
>>
>>  That should be able to print as you go - IBM APL does.  Right now there
>> is a significant delay - that I presume is unnecessarily using a
>> significant amount of memory to hold the formatted string.
>>
>> Of course, you still can't ^C out of that either - but that's a different
>> matter.
>>
>>  I understand that in many situations you must format the whole thing
>> before you can can see how it lays out.  But that is not true in cases
>> where it clearly doesn't fit (like ⍳100000) and many, many cases where it
>> is too large to have a reasonable format.  Those are the cases when
>> print-as-you-go can be done and would be without delay, and save
>> significant memory - and hopefully easier to interrupt.
>>
>>  Thanks.
>>
>>  Blake
>>
>>
>>
>>
>
>

Reply via email to