Andreas Leha writes:
> Exactly. I guess my implicit question was, whether we should aim to
> make :imagemagick accept 'no' as nil to be consistent with the general
> org babel conventions.
>
> As I get it, you would say: no.
Not at all. My main concern was to fix the issue. This is another one.
Hi Nicolas,
Nicolas Goaziou writes:
> Andreas Leha writes:
>
>> I am not sure about the possible values, though. babel header arguments
>> usually take 'yes' and 'no' as values for TRUE and FALSE.
>
> Which is, IMO, a mistake. Lisp has already some definition of TRUE and
> FALSE which is not la
Andreas Leha writes:
> I am not sure about the possible values, though. babel header arguments
> usually take 'yes' and 'no' as values for TRUE and FALSE.
Which is, IMO, a mistake. Lisp has already some definition of TRUE and
FALSE which is not language-centric.
> Examples are :tangle, :commen
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> I get a spurious linting warning
>> ,
>> | high Unknown header argument ":imagemagick"
>> `
>>
>> While that header argument should be valid for latex blocks.
>
> Assuming possible values for :imagemagick are nil
Hello,
Andreas Leha writes:
> I get a spurious linting warning
> ,
> | high Unknown header argument ":imagemagick"
> `
>
> While that header argument should be valid for latex blocks.
Assuming possible values for :imagemagick are nil and t, this is now
fixed in master.
Thank you.
Re
Hi all,
I get a spurious linting warning
,
| high Unknown header argument ":imagemagick"
`
While that header argument should be valid for latex blocks.
Regards,
Andreas
