Hi Nicolas, Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Andreas Leha <andreas.l...@med.uni-goettingen.de> 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.
I agree completely. > >> Examples are :tangle, :comments, etc. So, I have been using >> ':imagemagick yes' until now. >> >> But on the other hand ':imagemagick no' is not doing the expected >> thing. > > I looked at the source and every time, :imagemagick is treated as > a boolean, so "yes" and "no" are equivalent to t. 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. (The next question would be whether we live with inconsistency or whether we should switch the other header arguments backward incompatibly use t and nil as well...) > > At least, the declaration seems on par with the source. Yes, thanks! Andreas
