Oh, and here's the log from a failed session (without external APserver). I
forgot to include it in my previous email:
Reading config file /home/emartenson/src/apl/dist/etc/gnu-apl.d/preferences
...
config file /home/emartenson/.config/gnu-apl/preferences is not
present/readable
Network listener started. Connection information: mode:tcp addr:58991
connecting to 127.0.0.1 port 16366.
(this is expected to fail, unless APserver was started manually)
forking new APserver listening on TCP port 16366
connecting to 127.0.0.1 port 16366.
(this is supposed to succeed.)
::connect() to existing APserver failed: Connection refused
*** using local Svar_DB cache
PID is 23947
argc: 8
argv[0]: '/home/emartenson/src/apl/dist/bin/apl'
argv[1]: '--rawCIN'
argv[2]: '--emacs'
argv[3]: '-l'
argv[4]: '37'
argv[5]: '--emacs_arg'
argv[6]: '0'
argv[7]: '--silent'
uprefs.user_do_svars: 1
uprefs.system_do_svars: 1
uprefs.requested_id: 0
uprefs.requested_par: 0
id.proc: 1001 at ProcessorID.cc:72
APnnn_port: 0 at ProcessorID.cc:89
*** Failed to start APnnn: processor 1001 will not accept incoming shared
variable offers. Expect surprises.
Regards,
Elias
On 1 July 2014 18:31, Elias Mårtenson <loke...@gmail.com> 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
>>
>>
>>
>
