Re: [Bug-apl] Yet another editor thingy.

2018-08-02 Thread Hans-Peter Sorge
Hello Chris, thank you for this master piece. The line editing in GNU APL is a bit cumbersome. But the apl session gets blocked during editing (edif2). Currently I have no clue, how to analyze it. Thank you again. Hans-Peter Am 30.07.2018 um 20:52 schrieb Chris Moller: > > Thanks, Jürgen. >

[Bug-apl] quad IO bug

2018-08-02 Thread Hans-Peter Sorge
Hello Jürgen, this is off by one:   ∇qio_test [1] ⎕IO∇   qio_test 1   ⍎¨ 'qio_test' 'qio_test' 0 0 Naturally it affects indexing too. Greetings Hans-Peter

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Juergen Sauermann
Hi Hans-Peter, interesting. I am getting this:   ∇qio_test[⎕]∇     ∇ [0]   qio_test [1]   ⎕IO     ∇   ⍎¨'qio_test' 'qio_test' 1 1 Which SVN version are you using? ///

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Blake McBride
This is what I get: ⎕IO 1 ∇tt [1] ⎕IO [2] ∇ tt 1 ⍎¨'tt' 'tt' 0 0 )off blake@blake-sony ~ $ apl --version BUILDTAG: - Project:GNU APL Version / SVN: 1.7 / 1058M Build Date: 2018-07-25 00:10:21 UTC Build OS: Linux 4.4.0-130-ge

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Blake McBride
I get the same thing for SVN 1060 On Thu, Aug 2, 2018 at 8:01 AM Blake McBride wrote: > This is what I get: > > ⎕IO > 1 > ∇tt > [1] ⎕IO > [2] ∇ > tt > 1 > ⍎¨'tt' 'tt' > 0 > 0 > )off > > blake@blake-sony ~ $ apl --version > BUILDTAG: > - > Project:

Re: [Bug-apl] Yet another editor thingy.

2018-08-02 Thread Chris Moller
I thought I'd fixed the echo blocking! Actually, what seems to be happening is that APL is still running--you can enter an APL expression, press enter, and the result will show up on your screen--but keystroke echoing is somehow inhibited. There was a patch for this Jürgenput in for me that s

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Hans-Peter Sorge
Hello Jürgen, it's version 1.7 / 1060M.  In a clear WS. Greetings Hans-Peter Am 02.08.2018 um 14:23 schrieb Juergen Sauermann: > Hi Hans-Peter, > > interesting. I am getting this: > > > *  ∇qio_test[⎕]∇ >     ∇ > [0]   qio_test > [1]   ⎕IO >     ∇ >   ⍎¨'qio_test' 'qio_test' > 1 > 1* >

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Hans-Peter Sorge
Hello Jürgen, some drilling   ⍎'qio_test'  1   ⍎¨⊂'qio_test'  0 Greetings Hans-Peter Am 02.08.2018 um 14:23 schrieb Juergen Sauermann: > Hi Hans-Peter, > > interesting. I am getting this: > > > *  ∇qio_test[⎕]∇ >     ∇ > [0]   qio_test > [1]   ⎕IO >     ∇ >   ⍎¨'qio_test'

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Juergen Sauermann
Hi I can now reproduce it, it seems to occur only on 64 bit machines (strange enough). I will look into it. /// Jürgen On 08/02/2018 03:25 PM, Hans-Peter Sorge wrote: Hello Jürgen, some drilling

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Juergen Sauermann
Hi, fixed in *SVN 1061*. /// Jürgen On 08/02/2018 04:13 PM, Juergen Sauermann wrote: > Hi > > I can now reproduce it, it seems to occur only on 64 bit machines > (strange enough). > I will look into it. > > /// Jürgen > > > > On 08/02/2018 03:25 PM, Hans-Peter Sorge wrote: >> >> Hello Jürgen, >

Re: [Bug-apl] Yet another editor thingy.

2018-08-02 Thread Juergen Sauermann
Hi Chris, I am not entirely happy with your patch, in particular because I cannot judge which other effects it may have and which problem it actually solves. What I can see is that: You disable automatic flushing when you are waiting for an input character and get a ^C interrupt or so, What I d

Re: [Bug-apl] Yet another editor thingy.

2018-08-02 Thread Chris Moller
I agree with you.  I'm not all that pleased with it either, mostly because I don't understand why it works--it was something suggested by someone on StackOverflow. Whatever is going on seems to be the result of the EINTR out of the fgetc()--I'll try to look more closely at that.  I'll also try

Re: [Bug-apl] quad IO bug

2018-08-02 Thread Hans-Peter Sorge
Hi Jürgen, the fix is OK. Thank you, Hans-Peter Am 02.08.2018 um 17:01 schrieb Juergen Sauermann: > Hi, > > fixed in *SVN 1061*. > > /// Jürgen > > > On 08/02/2018 04:13 PM, Juergen Sauermann wrote: >> Hi >> >> I can now reproduce it, it seems to occur only on 64 bit machines >> (strange enoug