Eric,
Eric Schulte wrote:
Let me explain. AFAICT, there were 5 possibles values of the :colnames
header argument:
- no header argument :: (default for all languages but Emacs Lisp)
- :colnames no :: (default for Emacs Lisp code blocks)
- :colnames yes :: Tells Org Babel that your first row
Eric,
Eric Schulte wrote:
** 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:
Eric,
Eric Schulte wrote:
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?
Much clearer, but not yet crystal-clear for me...
Let me explain. AFAICT, there were 5 possibles values of the :colnames
header argument:
- no header argument :: (default for all languages but Emacs Lisp)
- :colnames no :: (default for Emacs Lisp code blocks)
- :colnames yes :: Tells Org
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has default
header arguments set to pass column names through to the code
** 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
Hi Eric,
Sebastien Vauban wrote:
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has default
header arguments set to pass column names through to the code block,
where the processing
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has
default header arguments set to pass column names
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has default
header arguments set to pass column names through to the code block, where
the processing may be done trivially in
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has default
header arguments set to pass column names through to the code block, where
the processing may be done trivially in
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Eric,
Eric Schulte wrote:
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has default
header arguments set to pass column names through to the code
Hi Seb,
Emacs Lisp is an exception in terms of colname processing, it has
default header arguments set to pass column names through to the code
block, where the processing may be done trivially in Emacs Lisp.
#+name: input
| id | var1 |
|--+--|
| obs1 | foo |
| obs2 | bar |
Hi Eric,
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has
default header arguments set to pass column names through to the code
block, where the processing may be done trivially in Emacs Lisp.
OK, but I don't understand the precedence of header arguments.
Sebastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Eric,
Eric Schulte wrote:
Emacs Lisp is an exception in terms of colname processing, it has
default header arguments set to pass column names through to the code
block, where the processing may be done trivially in Emacs Lisp.
OK, but
Hello,
Here are some tests with the colnames parameter *and* the Emacs Lisp language
for the echo code block. They're giving results I don't understand...
Note that functionally the same echo code block in other languages (I tested
R and sh) does return the expected results.
* Input table
15 matches
Mail list logo
