Multiple sessions and their logs
Posted: Tue Jun 22, 2021 4:44 pm
(I originally confused the "session_file" with "log_file" and "SaveSessionOnExit" with "SaveLogOnExit", but now realised the LOG of the session is separate from the SESSION.)
I frequently run two APL sessions in my PC at the same time, one for development, and the other running an application.
To aid this I have two shortcuts on my PC's desktop, one to start an APL development session, the other to run my "ANT" application.
In the registry:-
SaveLogOnExit is set to 1
and
log_file is set to:
C:\Users\Ray\Documents\Dyalog APL-64 18.0 Unicode Files\default.dlf
In my ANT's shortcut, the "target" has 3 entries (shown here as 3 separate lines) :
"C:\Program Files\Dyalog\Dyalog APL-64 18.0 Unicode\dyalog.exe"
start
LOADWS=C:\MiSites\hexserver31
Line one is simply the Dyalog executable (in quotes because of the embedded spaces within the full file path).
Line two is the name of the workspace I initially load, which sets up my pseudo user command. It also acts on my (not Dyalog's) command line parameter "LOADWS" if present.
Line three is that LOADWS parameter. On exit, "start.dws", ⎕LOADs the workspace named in this parameter. "hexserv31" in turn "bootstraps" the ANT application.
To this shortcut I have tried adding a standard Dyalog configuration parameter :
SaveLogOnExit=0
but this does not appear to override the registry entry, and the session log file is still being updated upon exit from the ANT application.
Surely, Configuration Parameters specified in the APL command line apply to the whole session, and so should over-ride the entries in the Registry, even following multiple ⎕LOADs .
Ray
I frequently run two APL sessions in my PC at the same time, one for development, and the other running an application.
To aid this I have two shortcuts on my PC's desktop, one to start an APL development session, the other to run my "ANT" application.
In the registry:-
SaveLogOnExit is set to 1
and
log_file is set to:
C:\Users\Ray\Documents\Dyalog APL-64 18.0 Unicode Files\default.dlf
In my ANT's shortcut, the "target" has 3 entries (shown here as 3 separate lines) :
"C:\Program Files\Dyalog\Dyalog APL-64 18.0 Unicode\dyalog.exe"
start
LOADWS=C:\MiSites\hexserver31
Line one is simply the Dyalog executable (in quotes because of the embedded spaces within the full file path).
Line two is the name of the workspace I initially load, which sets up my pseudo user command. It also acts on my (not Dyalog's) command line parameter "LOADWS" if present.
Line three is that LOADWS parameter. On exit, "start.dws", ⎕LOADs the workspace named in this parameter. "hexserv31" in turn "bootstraps" the ANT application.
To this shortcut I have tried adding a standard Dyalog configuration parameter :
SaveLogOnExit=0
but this does not appear to override the registry entry, and the session log file is still being updated upon exit from the ANT application.
Surely, Configuration Parameters specified in the APL command line apply to the whole session, and so should over-ride the entries in the Registry, even following multiple ⎕LOADs .
Ray