Nikolay, I do not have any objections concerning the last version of
your patch (I have not test it though). It is tracked on
https://updates.orgmode.org/ however it may take months before it will
be committed.
Have you signed FSF papers related to copyright? See
https://orgmode.org/worg/org-contribute.html#copyright There is no
"TINYCHANGE" keyword in the commit message and I have not found you in
the list of contributors to Org mode (Bastien likely have access to more
actual data). Since several your patches have been accepted to Emacs,
you are close to the limit when formalities become necessary.
Do not consider the comments below as a request to change anything in
the patch. I am just trying to express more clear what I wrote in the
previous message.
On 31/12/2021 03:54, Nikolay Kudryavtsev wrote:
When some external data is substituted into a Maxima command
(batchload this case) there should be an extra pass of escaping that
protects special characters like quotes (and backslashes?) accordingly
to Maxima rules.
Not necessarily, Maxima is capable of understanding unescaped paths, for
example, this works:
maxima --very-quiet -r "batchload(\"/tmp/sp
ce/babel-gxqTkM/maxima-ua3e9j.max\")"$
Consider a really peculiar path for tmp files with quotes
/tmp/")$ something-weird$ "/maxima-ua3e9j.max
I hope, it is unrealistic and will be properly escaped by %S formatter.
I am a bit surprised that Maxima does not allow to do it in a more
reliable way since several interfaces exist (WxMaxima, texmacs). Unsure
if get_application_args is suitable
https://sourceforge.net/p/maxima/mailman/message/35180908/
Command line Maxima actually has a batch flag, but using it returns the
entire input file in the output too and that seems to be the reason why
the original authors of ob-maxima didn't use it.
It would be great if it had another flag to suppress printing content of
the batch script or a flag that changes a setting that controls such
behavior.
