Maxima offers the (albeit undocumented) variables *prompt-prefix*
and *prompt-suffix*
that allow to make prompts machine-identifiable. But writers of front-ends might struggle to identify which type of prompt this is:
Perhaps one should add *question-prompt-prefix*
, *question-prompt-suffix*
etc. that are used, if set, instead for more specialized prompts. One could even add a *integer-question-prompt-prefix*
or *string-question-prompt-prefix*
with the according suffixes if one wants the front-end to be able to split question prompts into more specialized types, as well.
Diff:
As far as I can see, the
alt-display
package can do much of this at the moment. See the documentation foralt_display_output_type
here.Maxima's lisp and debugger printers are distinct from
displa
, the printer for the maxima repl. I am sure that it is not so hard to incorporate these withinalt-display
, though.Another lisp prompt is the built-in the lisp debugger itself. That would require more work (quirks, etc.) and is not worth the time, imo. If one accidentally lands there, it's most likely because maxima has crashed; otherwise, one is using the wrong tool to poke around the internals of maxima.
Finer-grained question types require
ask-sign
et. al. to provide more information about the question type.BTW, IMO, it would be really helpful for both projects if wxMaxima (and e/imaxima) adopted
alt-display
as its method to communicate with the frontend.Leo
If alt-display is a more standard way to do what wxMaxima is doing I am all for it. But I would need loads of help from a lisp wizard in order to switch to that method ...