[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can
From: |
Ihor Radchenko |
Subject: |
Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom) |
Date: |
Wed, 20 Sep 2023 09:17:54 +0000 |
Leo Butler <Leo.Butler@umanitoba.ca> writes:
>>>> May you clarify the purpose of "linenum"?
>> Do I understand correctly that the above will simply affect debug output
>> when maxima references where a problematic line is located in the source?
>
> No, it affects how output labels are printed. With this value, the
> "first" line in the source block receives the line number 1; without it,
> it would get 2.
Ok. This should be documented in the commit message and possibly in the
code itself.
>>
>>>>> (unless (or (string-match "batch" line)
>>>>> (string-match "^rat: replaced
>>>>> .*$" line)
>>>>> (string-match "^;;; Loading
>>>>> #P" line)
>>>>> + (string-match "^read and
>>>>> interpret" line)
>>>>> + (string-match
>>>>> "^(%\\([io]-?[0-9]+\\))[ ]+$" line)
>>>>
>>>> May you explain why you added these two conditions?
>>>
>
> <snip>
>
>>
>> May empty lines be intentional in some maxima code?
>
> A blank line is simply skipped by the maxima reader; an empty input line
> is a syntax error.
>
> However, "empty" output may appear, so I have modified that filter.
+ (string-match
"^(%\\([io]-?[0-9]+\\))[ ]+$" line)
It would be nice to add a comment line explaining what this regexp
matches against.
> * (org-babel-maxima--graphic-package-options): an alist of Maxima
> graphics packages and the Maxima code to set up that package.
This is a bit confusing. I'd say "A new variable storing alist of Maxima ..."
> * (org-babel-maxima--default-epilogue): an alist of the clean-up code
> that is run at end of a `graphical-output' or `non-graphical-output'
> source block.
Same here.
Basically, it should be clear from the commit message when you add new
variables and when you modify existing.
> * (org-babel-maxima-expand): prepare the source block for
> execution.
This is vague. Please explain what is changed in more details.
> * (org-babel-execute:maxima): use the :batch header argument and
> `org-babel-maxima--command-arguments-default' to execute the source
> block. Add a couple extra regexps to filter the output of a batch-ed
> source block.
This reads better compared to the above.
> +(defconst org-babel-header-args:maxima
> + '((batch . :any)
Why :any? Only two values are allowed here.
> + (graphics-pkg . :any))
Same. The value is a closed list.
> +(defvar org-babel-maxima--command-arguments-default
> + "--very-quiet"
> + "Command-line arguments sent to Maxima by default. If the
Please keep the first line as a single sentence.
See
https://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
> +(defvar org-babel-maxima--default-epilogue
> + '((graphical-output . "gnuplot_close ()$")
> + (non-graphical-output . ""))
> + "The final Maxima code executed in a source block. An alist with
Same problem with the first line.
--
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>
- 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/)], (continued)
- 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, 2023/09/02
- 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 <=
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Leo Butler, 2023/09/20
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Ihor Radchenko, 2023/09/21
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Leo Butler, 2023/09/21
- Re: [PATCH] ob-maxima.el, etc. (was Re: [MAINTENANCE] On how much we can expose internals into defcustom), Ihor Radchenko, 2023/09/22
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, 2023/09/02