>> ** Using =:colnames no= header argument (case 2) >> >> #+begin_src emacs-lisp :var data=unset-colnames-example-input :colnames no >> data >> #+end_src >> >> #+results: >> | a | b | >> |---+---| >> | 1 | 2 | >> | 3 | 4 | >> >> Here, I still don't understand why I do see the table header line: I >> did change the default =:colnames yes= specification to =:colnames >> no= on the code block. I did override the default value. Why is the >> =no= argument not respected? > > This still escapes me. >
Answered in my previous reply. > >> ** Using =:colnames ()= header argument (case 6) >> >> As you told me, to "unset" the =:colnames yes= header argument, we must use: >> >> #+begin_src emacs-lisp :var data=unset-colnames-example-input :colnames () >> data >> #+end_src >> >> #+results: >> | 1 | 2 | >> | 3 | 4 | >> >> That does work. >> >> What is still unclear to me as well, is why =()= and =nil= aren't the same >> from Babel's point of view? > > However, I think I understood this one: it is because nil is interpreted as a > string, not as the empty list; right? > > That's because strings aren't quoted, right? > Yes. Cheers, > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte