[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (r
From: |
Ihor Radchenko |
Subject: |
Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)] |
Date: |
Sat, 02 Sep 2023 07:19:50 +0000 |
Leo Butler <Leo.Butler@umanitoba.ca> writes:
> I think that your request may be handled by one of two improvements:
>
> 1. Implement session support in ob-maxima.el; and
> 2. Many of the design decisions in the existing ob-maxima code should be
> customizable.
> I am attaching a patch to address 2. Please try it out, I think that it
> will satisfy your requests. Feedback is welcome.
Thanks for the patch!
> +(defcustom org-babel-maxima-command-arguments
> + "--very-quiet"
> +(defcustom org-babel-maxima-batch/load
> + "batchload"
> +
> +(defcustom org-babel-maxima-graphic-file-format-string
> + "(set_plot_option ('[gnuplot_term, png]), set_plot_option
> ('[gnuplot_out_file, %S]))$"
> +
> +(defcustom org-babel-maxima-default-epilogue
> + "gnuplot_close ()$"
This might be fine, but may you please explain what would be the purpose
of customizing each of these options?
IMHO, in their current state, if a user mindlessly customizes these
options without knowing how ob-maxima internals work, ob-maxima may
simply be broken. It is also not very clear what would be the benefit
customizing any of the proposed options.
As a general rule, we do not expose internal details that are _required_
for things to work to users. In the above,
`org-babel-maxima-default-epilogue' appears to be paired with
`org-babel-maxima-graphic-file-format-string' and may need to be changed
depending on its value. Also, I am not sure if removing --very-quiet may
not affect :results output.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
- [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)], Lockywolf, 2023/09/01
- Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)], Leo Butler, 2023/09/01
- Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)],
Ihor Radchenko <=
- Re: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)], Leo Butler, 2023/09/02
- [MAINTENANCE] On how much we can expose internals into defcustom (was: [BUG] Consider replacing bachload with batch in ob-maxima. [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]), Ihor Radchenko, 2023/09/05
- Re: [MAINTENANCE] On how much we can expose internals into defcustom, Leo Butler, 2023/09/06
- Re: [MAINTENANCE] On how much we can expose internals into defcustom, Ihor Radchenko, 2023/09/07
- [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Leo Butler, 2023/09/12
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Ihor Radchenko, 2023/09/15
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Leo Butler, 2023/09/15
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Ihor Radchenko, 2023/09/16
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Leo Butler, 2023/09/19
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Ihor Radchenko, 2023/09/20