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 14:45:52 +0100 Message-ID: References: <86oaqbrl35.fsf@example.com> 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]:34319) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8r2x-0004sb-Hg for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 08:53:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y8r2s-00059S-I9 for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 08:53:15 -0500 Received: from plane.gmane.org ([80.91.229.3]:59139) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y8r2s-00057u-Bv for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 08:53:10 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y8qxw-0002CC-Ri for emacs-orgmode@gnu.org; Wed, 07 Jan 2015 14:48:04 +0100 In-Reply-To: <86oaqbrl35.fsf@example.com> (Sebastien Vauban's message of "Wed, 07 Jan 2015 10:33:50 +0100") 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: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Sebastien Vauban writes: > Thomas S. Dye wrote: >> Rainer M Krug 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 =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) iQEcBAEBAgAGBQJUrTiVAAoJENvXNx4PUvmCGcwH/RmIm9PZePnBY/RWUPcT5qz4 IvFucUvg/lHz67ftxrGUVUSOLO7ZsvhX0kUEYF/XzApM6BBEdsPNRaZ3UmbDg2AM k8fajqdvYD6naPYhOgrscMP3DLFXvnn7HP2phCQc7C2CYJOh+W/rj3TOvDqk6+TL 2/1liBRzFHg96K952ZaI+1ExZ4VPEpEIrlltJ6UEnhPsFwF90PHr9YedkBFbcfkW uVWYEaGp3XiWI91zU7PyLG7HDiFvdhupmD3x7GGSEXUi/eUpMh36+Or8IUdtXNY8 8GBOAWW2qnjFHGB9QnRGu53iepQpoAeASrTqZY2hZKI1vrbU8XofQav+I/yunrM= =2ejF -----END PGP SIGNATURE----- --=-=-=--