From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Subject: Re: [babel, bug?] colnames with a list of columns does not work
Date: Fri, 23 Jan 2015 11:35:29 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
Hello Thomas and Rainer,
Rainer M Krug wrote:
> Sebastien Vauban writes:
>> #+begin_src R :rownames yes :colnames '(Lg Nb)
>> head(table(iris$Petal.Length, iris$Species)[, "setosa"], n=2)
>> | | x |
>> | 1 | 1 |
>> | 1.1 | 1 |
>> while I was expecting:
>> | Lg | Nb |
>> | 1 | 1 |
>> | 1.1 | 1 |
> WHy should it? The org-info manual states:
> | The `:colnames' header argument accepts the values `yes', `no', or
> | `nil' for unassigned. The default value is `nil'. Note that the
> | behavior of the `:colnames' header argument may differ across
> | languages.
> It says nothing about accepting any other values.
> Unless I am missing something?
Yes, you just show that the documentation is not up-to-date, as that
functionality *is* implemented for most languages.
Doing some bit of archeology, I just found out that:
- Eric wrote a patch to support the above (but it hasn't be applied),
- I (!) even wrote a test of that functionality (for a shell block) in
│ It looks like ob-R implements its own result table reconstruction
│ instead of using the general support. This is because R actually
│ has a notion of column names and row names internally. The
│ implementation in ob-R does not correctly handle specified colnames
│ as your example shows.
│ The attached patch brings ob-R closer to the using the unified
│ general table reconstructed used in most other languages, and fixes
│ your problem mentioned above. I haven't applied it however, as it
│ may introduce other bugs related to specifying column names from
│ within R. For example, I'm not sure that it will now correctly
│ apply column names from a table built entirely from within R.
│ Additional testing by someone more familiar with R than myself would
│ be greatly appreciated.
Should such someone (more familiar with R) be able to confirm that his
patch work without introducing problems, it could be applied so that
R should behave the same as in most languages...
next prev parent reply other threads:[~2015-01-23 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 10:56 [babel, bug?] colnames with a list of columns does not work Sebastien Vauban
2015-01-22 15:37 ` Thomas S. Dye
2015-01-22 16:47 ` Rainer M Krug
2015-01-23 10:35 ` Sebastien Vauban [this message]
2015-01-23 11:13 ` Rainer M Krug
2015-01-23 19:49 ` Aaron Ecay
2015-01-23 20:00 ` Thomas S. Dye
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).