From: Rainer M Krug <Rainer@krugs.de>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [BUG] [babel] [R] :colnames yes conflicts with :results file
Date: Wed, 07 Jan 2015 14:45:52 +0100 [thread overview]
Message-ID: <m2a91u3drj.fsf@krugs.de> (raw)
In-Reply-To: <86oaqbrl35.fsf@example.com> (Sebastien Vauban's message of "Wed, 07 Jan 2015 10:33:50 +0100")
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> Thomas S. Dye wrote:
>> Rainer M Krug <Rainer-vfylz/Ys1k4@public.gmane.org> writes:
>>> But the :colnames only works on tables (i.e. :results table) - but
>>> the result is represented as a link to a file. So what should happen?
>>
>> I think this is mistaken. "Tables" occur in at least three contexts
>> in babel source code blocks. There are input tables, :var mytable,
>> there are "tables" within the code block, represented in R as
>> a dataframe or a matrix, and there are output tables, which are placed
>> in the Org mode buffer as a result.
>>
>> I use :colnames to keep the column names of input tables associated
>> with the "tables" within the code block, and typically have them
>> represented in the output, whether that is a "table" written to file,
>> or output to the Org mode buffer as an Org mode table, either by
>> default or (more rarely) through use of :results table.
>>
>> In my experience :results table is mostly useful for coercing a value
>> that babel would otherwise interpret as a scalar into a single element
>> table.
>
> Another problem, IIUC, is that :colnames serves to specify both input
> and output, right?
This would be the optimal solution - but instead of having a second
header argument, the values ~input~ and ~output~ and ~both~ could be added,
allowing to have headers only for input or output respectively, or for
both (equivalent to ~yes~ at the moment, but clearer).
>
> Or can you well declare that, for example, the input table has an
> header, but to strip it from the output??
I would prefer the option to be able to specify :colnames and :rownames
for input and output separately.
Cheers,
Rainer
>
> Best regards,
> Seb
--
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]
prev parent reply other threads:[~2015-01-07 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 12:40 [BUG] [babel] [R] :colnames yes conflicts with :results file Andreas Leha
2015-01-06 13:49 ` Rainer M Krug
2015-01-06 15:39 ` Andreas Leha
2015-01-06 17:50 ` Aaron Ecay
2015-01-07 9:11 ` Rainer M Krug
2015-01-06 16:01 ` Thomas S. Dye
2015-01-07 9:19 ` Rainer M Krug
2015-01-07 17:14 ` Thomas S. Dye
2015-01-07 9:33 ` Sebastien Vauban
2015-01-07 13:45 ` Rainer M Krug [this message]
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a91u3drj.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).