From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer M Krug Subject: Re: [BUG] [babel] [R] :colnames yes conflicts with :results file Date: Wed, 07 Jan 2015 10:19:10 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51692) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8rrU-0007qo-HR for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 09:45:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y8rrL-0004IH-0o for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 09:45:28 -0500 Received: from mail-wg0-f52.google.com ([74.125.82.52]:62590) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8rrK-0004I6-SL for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 09:45:18 -0500 Received: by mail-wg0-f52.google.com with SMTP id x12so1292708wgg.25 for ; Wed, 07 Jan 2015 06:45:17 -0800 (PST) In-Reply-To: (Thomas S. Dye's message of "Tue, 06 Jan 2015 06:01:02 -1000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Thomas S. Dye" Cc: Andreas Leha , emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable tsd@tsdye.com (Thomas S. Dye) writes: > Aloha Rainer, > > Rainer M Krug 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'.=20 >> `---- >> >> 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. Agreed - I was only thinking of the R -> org path. > > 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. Well - if the result is an R data.frame, it would not make a difference if I use :results table or not - correct? > >> 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. Yup - ~:colnames yes :results file~ as well as ~:colnames yes :results table~ are not Cheers, Rainer > > All the best, > Tom =2D-=20 Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBAgAGBQJUrPoOAAoJENvXNx4PUvmCqpIIAJQHZ4qO13hDWW01PNEW5z5T GpvMeVzwpD9zuETMd59d0P1QwxOiDegpvsq68CjGwVflBd1p/OfhlIzenT4V5yjG tNp45J+yWDIx+V/hBvYL9Nv3z/4CrE7oKX12y/RlwM1XhppHFRH3cOaid8/9FN7r 6hVKWIC/TAxb0z1CJ8BTY5+CwAmts4jv0r5IDe6pE0AKpEAs9sCloho2gKSRUfsO v6j7OGQoKlCPLPEEe90xOPAcZ5t/mvkV0JGDnvuOvKELln4nVd7Ni1R3Npu7KQL+ XKkIXaHQIvRnKU7d20jMaEbm7+P1FDsS+11HgKPLdSxrO5sso1d3JXkI00UYzzo= =ET5W -----END PGP SIGNATURE----- --=-=-=--