You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our org heavily uses the -r command line option in a Linux environment for various scripts. While matlab-proxy does support some startup code execution, the fact that no output is displayed in the command window makes debugging a challenge and the feature overall less useful. Would it be possible to have the startup code from the command window, or perhaps add another env variable for this?
Thanks.
The text was updated successfully, but these errors were encountered:
Dear @dnmiller, thank you for using matlab-proxy package!
Would it help in your case if the output of executing custom MATLAB startup code is saved in a file on your file system? (assuming the output is not suppressed using a semi-colon). If yes, then the feature is currently available in the product.
The file containing the output of this startup code gets saved in <HOME-DIR>\.matlab\MWI\hosts\<HOSTNAME>\ports\<MATLAB-PROXY-PORT>\startup_code_output.txt. The path to this file is also displayed in the terminal when we access matlab-proxy endpoint.
Hello,
Our org heavily uses the -r command line option in a Linux environment for various scripts. While matlab-proxy does support some startup code execution, the fact that no output is displayed in the command window makes debugging a challenge and the feature overall less useful. Would it be possible to have the startup code from the command window, or perhaps add another env variable for this?
Thanks.
The text was updated successfully, but these errors were encountered: