-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There does not seem to be a function to_lisp() #1785
Comments
There is no
But it seems not work in a current wxMaxima, you are right. And it seemed to work in older version (19.07.0, included in Ubuntu 20.04). |
This is because the lisp-quiet function turns off the prompt. The lisp-quiet function is called sometime during the printing of a cell. |
I got the to_lisp () function to work when I added the following lines of code at the start of to_lisp. However, the lisp-quiet function may still cause issues with follow-up statements in Wxmaxima. |
The lisp-quiet function needs to be replaced with a bit bucket in the WxMaxima program and just leave the prompt on. |
I still hope that one day the Maxima project will make that function work correctly: If we leave the prompt on the input and output label numbers will be a bit unpredictable. |
Couldn't you make it just ignore the return text and also ignore the changing of the cell number for the input and output cell labels? This would not work if the label count is done in Maxima, but I guess a flag could also be sent to Maxima to not change the cell number. |
If wxMaxima would display a different label number tha.n the one Maxima assigns to a label users who use the label numbers would complain that ...and Maxima has a flag that tells not to advance the label numbers and not to remember the current command's output. It is named , |
@gunterkoenigsmann I gather that there is some problem with |
My program just hangs up at this point.
If you don't disable the prompt for lisp-quiet, can you let WxMaxima just ignore the text that comes back from lisp-quiet?
The text was updated successfully, but these errors were encountered: