How to pass start-up system parameters in newlisp-tk

[jrichter]

Hi

I would like a tip to start newlisp-tk passing -s (stack size) to specify
a diferent default.

I have tried to change the "properties" in the start-up icon from:
"C:\Program Files\newlisp\newlisp-tk.exe"

to

"C:\Program Files\newlisp\newlisp-tk.exe" "-s 10000"

but it did not worked.

The HTML newlisp-tk dcumentation did not clarified how to pass newlisp
start-up options.

Could anyone help me.

Thanks

[HPW]

Not an easy question.
I am not aware of a command to modify the stack of a running newLISP.
We can only use the commandline-switch of the newLISP.exe.

In newLISP-tk we have the additional layer of TK.
There we can access the commandline-args via '(tk-args)' but there
we are to late because newLISP.exe is running yet.

The only thing I can think of in the moment is to change 'newlisp-tk.tcl'-source like this:

Code: Select all

# start local copy of newLISP only if running newLISP and newLISP-tk on the same host
# else assume that newLISP already has been started at the remote $Ide(newLISPhost)
if { $remoteFlag == 0 } {
	set newLISPpid [exec $Ide(newLISPbin)/newlisp -p $Ide(newLISPport) -s 10000 &] }

# connect to newLISP

or Lutz make a new var in 'newlisp-tk.config' called

set Ide(newLISPstack) "1024"

Code: Select all

# start local copy of newLISP only if running newLISP and newLISP-tk on the same host
# else assume that newLISP already has been started at the remote $Ide(newLISPhost)
if { $remoteFlag == 0 } {
	set newLISPpid [exec $Ide(newLISPbin)/newlisp -p $Ide(newLISPport) -s $Ide(newLISPstack) &] }

# connect to newLISP

Later: Just tried both ways and it works as expected. So Lutz can consider this change and take it into the wrapped distribution.

[jrichter]

Not an easy question.
I am not aware of a command to modify the stack of a running newLISP.
We can only use the commandline-switch of the newLISP.exe.

In newLISP-tk we have the additional layer of TK.
There we can access the commandline-args via '(tk-args)' but there
we are to late because newLISP.exe is running yet.

The only thing I can think of in the moment is to change 'newlisp-tk.tcl'-source like this:

Code: Select all

# start local copy of newLISP only if running newLISP and newLISP-tk on the same host
# else assume that newLISP already has been started at the remote $Ide(newLISPhost)
if { $remoteFlag == 0 } {
	set newLISPpid [exec $Ide(newLISPbin)/newlisp -p $Ide(newLISPport) -s 10000 &] }

# connect to newLISP

or Lutz make a new var in 'newlisp-tk.config' called

set Ide(newLISPstack) "1024"

Code: Select all

# start local copy of newLISP only if running newLISP and newLISP-tk on the same host
# else assume that newLISP already has been started at the remote $Ide(newLISPhost)
if { $remoteFlag == 0 } {
	set newLISPpid [exec $Ide(newLISPbin)/newlisp -p $Ide(newLISPport) -s $Ide(newLISPstack) &] }

# connect to newLISP

Later: Just tried both ways and it works as expected. So Lutz can consider this change and take it into the wrapped distribution.

Could also do 'complete' job and expand this solution to cover ALL newlisp
start up options

[HPW]

Could also do 'complete' job and expand this solution to cover ALL newlisp
start up options

Not much other options there which would make sense with neweLISP-TK:

-m = would be usefull here too!
-c = make no sense here, no visible console window
-d = make no sense here
-x = make no sense here
-e = make no sense here
-h = make no sense here

So 'Stack Size' and 'Memory Usage' remains for newLISP-Tk to set.