On Wed, Oct 04 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> Attached is:
>>
>> - my previous patch, rebased against the latest HEAD and only modified
>> to include a patch to etc/ORG-NEWS
>> - a patch to the worg docs that corrects the urls
>> - a patch to the worg docs that
Leo Butler writes:
> Attached is:
>
> - my previous patch, rebased against the latest HEAD and only modified
> to include a patch to etc/ORG-NEWS
> - a patch to the worg docs that corrects the urls
> - a patch to the worg docs that documents the new header arguments and
> provides examples
On Fri, Sep 22 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>>> What is the purpose of this `unwind-protect'?
>>> In its current form, it does nothing because no UNWINDFORMS are
>>> provided.
>>
>> I copied the forms from tests I had written for ob-octave, without
>> thinking about why
Leo Butler writes:
>> What is the purpose of this `unwind-protect'?
>> In its current form, it does nothing because no UNWINDFORMS are
>> provided.
>
> I copied the forms from tests I had written for ob-octave, without
> thinking about why those tests were wrapped in an `unwind-protect'
> form.
On Thu, Sep 21 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
+(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.
>>
>> I
Leo Butler writes:
>>> +(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.
>
> I have made the change requested.
>
> However, beyond the
On Wed, Sep 20 2023, Ihor Radchenko wrote:
> Leo Butler 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
Leo Butler 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
>
On Sat, Sep 16 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>>> Also, non-standard arguments should be defined in
>>> `org-babel-header-args:maxima'.
>>>
>>
>> Ok. I see that some packages (e.g. ob-gnuplot.el) use a `defvar' form,
>> while others (e.g. ob-R.el) use a `defconst' form. Is
Leo Butler writes:
>> Also, non-standard arguments should be defined in
>> `org-babel-header-args:maxima'.
>>
>
> Ok. I see that some packages (e.g. ob-gnuplot.el) use a `defvar' form,
> while others (e.g. ob-R.el) use a `defconst' form. Is there a preference?
defconst I think. The value is
On Fri, Sep 15 2023, Ihor Radchenko wrote:
> Leo Butler writes:
>
>> Attached is a patch that tries to address some of Ihor's concerns. I
>> have added two header arguments for maxima src blocks:
>
> Thanks!
>
>> - :graphics-pkg lets the user choose the graphics package to use;
>>
>> - :batch
Leo Butler writes:
> Attached is a patch that tries to address some of Ihor's concerns. I
> have added two header arguments for maxima src blocks:
Thanks!
> - :graphics-pkg lets the user choose the graphics package to use;
>
> - :batch lets the user choose which source-code loader Maxima will
12 matches
Mail list logo
