Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Juergen Sauermann
Hi Alexey, we already have Elias' emacs support for GNU APL, which I believe is a good replacement for IBM's built-in full-screen editor (aka editor 2). And a number of other editors have been proposed in the past, for example Blakes's editor (see htt

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Alexey Veretennikov
Actually it is a great thread, I also agree with Christian what the full-text editor support should be a part of interpreter (as it is in IBM APL2 and Dyalog). Kacper Gutowski writes: > On Tue, Dec 20, 2016 at 10:30:14AM +0100, Alexey Veretennikov wrote: >> Using )HOST Vim complains "Vim: Warnin

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Kacper Gutowski
On Tue, Dec 20, 2016 at 10:30:14AM +0100, Alexey Veretennikov wrote: > Using )HOST Vim complains "Vim: Warning: Output is not to a terminal" > and not really useful (can't see what I type for instance). > Same if I use popen() via ⎕FIO. )HOST and popen are essentially the same thing and they both

Re: [Bug-apl] how to read utf-8 file into the APL string

2016-12-20 Thread Alexey Veretennikov
Thanks! Works as charm! Juergen Sauermann writes: > Hi Alexey, > > you can probably use 18⎕CR and 19 ⎕CR to convert beween the bytes read > from an UTF8 encoded file and the characters being encoded (and back). > > See section 3.3 Dyadic ⎕CR in info apl. > > /// Jürgen > > On 12/20/2016 01:39 PM

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Juergen Sauermann
Hi Alexey, I see. You don't need X, but you need at least something inside which the editor runs. Almost every editor changes the terminal settings in one way or another. Therefore running an editor in the same window as GNU APL can and will most likely not work and is IMHO also not desirab

Re: [Bug-apl] how to read utf-8 file into the APL string

2016-12-20 Thread Juergen Sauermann
Hi Alexey, you can probably use 18⎕CR and 19 ⎕CR to convert beween the bytes read from an UTF8 encoded file and the characters being encoded (and back). See section 3.3 Dyadic ⎕CR in info apl. /// Jürgen On 12/20/20

[Bug-apl] how to read utf-8 file into the APL string

2016-12-20 Thread Alexey Veretennikov
Hi, I'm trying to read the file in UTF8 to the APL string. Using the following: )HOST 'cat' '/tmp/f.apl' ∇R←f x R←x+1 0 fun ← FIO∆read_file '/tmp/f.apl' fun ∇R←f x R←x+1 Which is apparently broken. -- Br, /Alexey

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Alexey Veretennikov
I meant running without X. But in my case I have X anyway, just didn't want to create another window. Juergen Sauermann writes: > Hi Alexey, > > not sure what you mean by 'console mode'? > > /// Jürgen > > On 12/20/2016 01:13 PM, Alexey Veretennikov wrote: > > Thanks, by launchig via external t

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Juergen Sauermann
Hi Alexey, not sure what you mean by 'console mode'? /// Jürgen On 12/20/2016 01:13 PM, Alexey Veretennikov wrote: Thanks, by launchig via external terminal it works (but it will not work in console mode :( ). Juergen Sauer

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Alexey Veretennikov
Thanks, by launchig via external terminal it works (but it will not work in console mode :( ). Juergen Sauermann writes: > Hi Alexey, > > try e.g.: > > )HOST xterm vim > > /// Jürgen > > On 12/20/2016 10:30 AM, Alexey Veretennikov wrote: > > Hi, > > Using )HOST Vim complains "Vim: Warning: Outp

Re: [Bug-apl] user commands in config file

2016-12-20 Thread Juergen Sauermann
Hi Alexey, the easiest way to achieve both is to have a workspace named CONTINUE in library 0 (library 0 is by default the directory named workspaces, but that can be changed in the preference file(s)). If that workspace exists then it will be

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Juergen Sauermann
Hi Alexey, try e.g.: )HOST xterm vim /// Jürgen On 12/20/2016 10:30 AM, Alexey Veretennikov wrote: Hi, Using )HOST Vim complains "Vim: Warning: Output is not to a terminal" and not really useful (can't see what

Re: [Bug-apl] Documentation/examples on system functions

2016-12-20 Thread Juergen Sauermann
Hi Alexey, The majority of GNU APL functions and commands are described in the IBM APL2 documentation which is available on the web. That documentations is better than anything I could possible write, so I did not even try. The functions

[Bug-apl] Documentation/examples on system functions

2016-12-20 Thread Alexey Veretennikov
Hi, I'm missing any information on system functions. The 'official' documentation only explains handful of functions. The ]help command just lists the functions. For example FIO function I had to type it with the intentional error in the argument to get the list of possible options (!!!) I can't f

Re: [Bug-apl] Calling external editor from APL session

2016-12-20 Thread Alexey Veretennikov
Hi, Using )HOST Vim complains "Vim: Warning: Output is not to a terminal" and not really useful (can't see what I type for instance). Same if I use popen() via ⎕FIO. juergen Sauermann writes: > Hi Alexey, > > it is possible though not very convenient:. You could write > a function doing the fol

Re: [Bug-apl] Bug: cannot erase incorrectly defined function

2016-12-20 Thread Elias Mårtenson
The function is probably still on the SI stack. Try running )SIC first. On 20 December 2016 at 16:45, Alexey Veretennikov < alexey.veretenni...@gmail.com> wrote: > Hi, > > If the function is incorrectly defined with the line-editor, it is > impossible to erase it: > > > )clear > CLEAR WS >

[Bug-apl] Bug: cannot erase incorrectly defined function

2016-12-20 Thread Alexey Veretennikov
Hi, If the function is incorrectly defined with the line-editor, it is impossible to erase it: )clear CLEAR WS ∇g [1] R←x+1 [2] ∇ g 10 VALUE ERROR g[1] R←x+1 ^ g VALUE ERROR g[1] R←x+1 ^ )erase g NOT ERASED: g )fns g ∇R←f x [1] R←x+