A boolean, default
A string or
A client-remote-debugging or
If new-process-p is non-nil (the default), then a new Lisp process is created to start the Listener and run the read-eval-print loop. This process runs until the read-eval-print loop exits. If new-process-p is
nil, then the read-eval-print loop runs in the current process and
start-remote-listener does not return until the read-eval-print loop exits.
nil) controls which connection to use. If connection is non-nil and is connected then it is used. Otherwise
start-remote-listener uses the same mechanism as the debugger to find the connection, which by default means re-using an existing connection if one exists, or opening a new one (under the control of the remote debugging spec). In typical usage, this be set up by either configure-remote-debugging-spec or start-client-remote-debugging-server. See Simple usage and Advanced usage - multiple connections for details.
close-on-exit is used only when connection is non-nil. When close-on-exit is non-nil, the connection is closed when the read-eval-print loop exits. Otherwise (the default), the connection remains open for later re-use.
If the Listener tool on the IDE side is closed, then the read-eval-print loop exits. Normally this is the only way that the loop exits, but you could also exit it by throwing to a surrounding catch (when new-process-p is
nil) or by terminating the process (by current-process-kill).
nil if connection is not a valid connection (either
nil or already closed) and it cannot find the connection to use. Otherwise, if new-process-p is non-nil (the default) it returns
t immediately, and if new-process-p is
nil it returns
nil only when the Listener is closed.
LispWorks User Guide and Reference Manual - 20 Sep 2017