From: tsd@tsdye.com (Thomas S. Dye)
To: Rainer M Krug <Rainer@krugs.de>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: [BUG] [babel] [R] :colnames yes conflicts with :results file
Date: Tue, 06 Jan 2015 06:01:02 -1000 [thread overview]
Message-ID: <m2wq4z6gqp.fsf@tsdye.com> (raw)
In-Reply-To: <m2oaqc3toj.fsf@krugs.de> (Rainer M. Krug's message of "Tue, 06 Jan 2015 14:49:48 +0100")
Aloha Rainer,
Rainer M Krug <Rainer@krugs.de> writes:
> I don't think this is a bug as it is not clear what should happen.
> In the org manual it states concerning the :results file
>
> ,----
> | * `file' The results will be interpreted as the path to a file, and
> | will be inserted into the Org mode buffer as a file link. E.g.,
> | `:results value file'.
> `----
>
> 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.
> If you would like to have a table with links to files, the easiest is to
> put the file names into [[]] in R and then return them in a table - or
> use :results output and "draw" the table.
>
> But as it stands, these two header arguments do not go together.
Which two header arguments? :results table file is contradictory, but
:colnames yes :results file is not, or should not be, IMHO.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-01-06 16:01 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 [this message]
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
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=m2wq4z6gqp.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=Rainer@krugs.de \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.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).