Hi Elias,
I have changed the max. interval from 500ms to 1 second. SVN 415.
I believe changing to single ^C via configuration would be more confusing
than helpful because the behavior under emacs (i.e. INTERRUPT =
ATTENTION) would deviate
from the behavior outside emacs (INTERRUPT ≠
Thank you. I think this will work better.
Regards,
Elias
On 5 Aug 2014 01:50, Juergen Sauermann juergen.sauerm...@t-online.de
wrote:
Hi Elias,
I have changed the max. interval from 500ms to 1 second. SVN 415.
I believe changing to single ^C via configuration would be more confusing
than
Hi Elias,
mapping two ^C to one is maybe not so good an idea.
IBM APL2 distinguishes between interrupt and attention and they have
different keys for that. interrupt interrupts execution immediately while
attention interrupts execution at the end of the statement.
Currently GNU APL is behaving
Control-C is a general prefix character in Emacs. In other words, you press
C-c followed by another keypress to execute a given function. C-c C-c
(i.e. Control-C twice) is defined to send a single control-c to an
underlying process (it's part of the framework that manages external
programs, of
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
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
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 ⍳10
That should be able to print as you go - IBM APL does. Right now there is
a significant delay -
Hi Blake,
I guess the proposed solution for both was ⎕SYL. Like:
* ⎕SYL[27] ← 1*
/// Jürgen
On 07/21/2014 12:26 AM, Blake McBride wrote:
Are my two items below a dead issue?
Thanks!
Blake
On Tue, Jul 8, 2014 at 9:58 PM, Blake McBride blake1...@gmail.com
Dear Juergen,
I don't think that really solves the problem because:
A. You have to remember to set it - and then to set it only to get around
what amounts to a bug - not being able to hit ^C
B. Whatever you set it to, you still have a problem with lengths that
approach that length.
C. What
Hi Blake,
unfortunately the rules for APL output are such that you cannot print
as you go.
For example before printing the second item in the first row, the first
column must have
been formatted completely in order to know the width of the first column.
I will see what I can do for
Are my two items below a dead issue?
Thanks!
Blake
On Tue, Jul 8, 2014 at 9:58 PM, Blake McBride blake1...@gmail.com wrote:
I think the layout function need two modifications:
1. enable ^C
2. at least for large data, output as you go rather than format the whole
thing and then output
I wouldn't do that!
On Tue, Jul 8, 2014 at 10:01 PM, Elias Mårtenson loke...@gmail.com wrote:
I suggested some time ago that very large data sets shouldn't be displayed
at all, since they are not only slow, they are also largely useless in an
interactive session.
It was decided that this
Hi,
not so. I implemented ⎕SYL[⎕IO+26;] for that case. Just try:
* ⎕SYL[⎕IO+26]←2000
⍳100
...*
/// Jürgen
On 07/09/2014 05:11 AM, Elias Mårtenson wrote:
Yeah, and neither would Jürgen. Seems like I was in the minority on
that one. :-)
Regards,
Elias
On 9 July 2014
I just tried this on IBM APL 2 on a machine with much less memory than the
machine I use for GNU APL. Interestingly, the ⍳100 had no delay. It
started printing immediately. Perhaps we can use a different algorithm for
display. One that starts printing immediately, and one that, presumably,
If I do:
z←⍳100
the operation is very fast. But if I do:
⍳100
it is very slow, presumably because it is formatting the whole thing for
display. No problem.
The problem is that during its effort to format for display, I cannot use
^C. ^C appears to work fine in normal
In Sharp APL (IPSA) we had a panic int which interrupted whatever was being
computed after a predetermined time.
It was inherent to the interpreter because we ran a timesharing system.
I don't recall the exact details but it went something like this;
1) Workspace gets swapped in for execution
There is already the SIGINT signal which is processed by GNU APL to
interrupt a function execution. However, this interruptability is not
extended to the layout function.
On 9 July 2014 09:09, Peter Teeson peter.tee...@icloud.com wrote:
In Sharp APL (IPSA) we had a panic int which interrupted
I think the layout function need two modifications:
1. enable ^C
2. at least for large data, output as you go rather than format the whole
thing and then output the whole thing
--blake
On Tue, Jul 8, 2014 at 9:27 PM, Elias Mårtenson loke...@gmail.com wrote:
There is already the SIGINT
I suggested some time ago that very large data sets shouldn't be displayed
at all, since they are not only slow, they are also largely useless in an
interactive session.
It was decided that this approach would not be taken, but I don't remember
the justification for it.
Regards,
Elias
On 9
Yeah, and neither would Jürgen. Seems like I was in the minority on that
one. :-)
Regards,
Elias
On 9 July 2014 11:10, Blake McBride blake1...@gmail.com wrote:
I wouldn't do that!
On Tue, Jul 8, 2014 at 10:01 PM, Elias Mårtenson loke...@gmail.com
wrote:
I suggested some time ago that
20 matches
Mail list logo
