My apl is 64-bit though. Both on Arch where it fails and on Ubuntu where it works.
Also, remember that it only happens when run inside of Emacs. I still think it's the timing issue. Regards, Elias On 1 July 2014 19:12, Juergen Sauermann <juergen.sauerm...@t-online.de> wrote: > Hi, > > there seems to be some type size confusion on 32-bit machines. The code > runs on my > 64-bit linux but not on my 32-bit linux. I'll look into this. > > /// Jürgen > > > > On 07/01/2014 12:31 PM, Elias Mårtenson wrote: > > This is weird. I only get the error when starting GNU APL from within > Emacs. When I start it manually, using exactly the same arguments > (including the --emacs part) it doesn't fail. > > If I manually start APserver and run apl from Emacs it also works > correctly. > > When I *do* get the error, the APserver is actually started (I can see > it using ps) but I still get the error. > > It seems to me as though when GNU APL is started within Emacs, the > APserver doesn't have time to initialise before apl attempts to connect > to it. That's the only explanation I can come up with right now. > > Regards, > Elias > > > On 1 July 2014 17:57, Juergen Sauermann <juergen.sauerm...@t-online.de> > wrote: > >> Hi ELias, >> >> sorry, my fault. Should have been -l 37 >> >> >> >> On 07/01/2014 08:41 AM, Elias Mårtenson wrote: >> >> Thank you. I tried to use the -l flag for apl, but it says the argument >> is not accepted. >> >> $ dist/bin/apl -l37 >> unknown option '-l37' >> >> Regards, >> Elias >> >> >> > >
