From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: [BUG] [babel] [R] :colnames yes conflicts with :results file Date: Wed, 07 Jan 2015 10:33:50 +0100 Message-ID: <86oaqbrl35.fsf@example.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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? Or can you well declare that, for example, the input table has an header, but to strip it from the output?? Best regards, Seb -- Sebastien Vauban