Re: Bug: Org export to latex produces incorrect table [8.3beta (release_8.3beta-1157-g8ddb84 @ /home/malsburg/usr/share/emacs/site-lisp/org/)]

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Titus von der Malsburg <malsburg@posteo.de> writes:

> On 2015-05-24 Sun 10:09, Thomas S. Dye wrote:
>> Titus von der Malsburg <malsburg@posteo.de> writes:
>>
>>> On 2015-05-24 Sun 08:36, Thomas S. Dye wrote:
>>>> Titus von der Malsburg <malsburg@posteo.de> writes:
>>>>
>>>>>> You got the result of rownames(x), which is expected.  The table you
>>>>>> expect is given by the following code:
>>>>>
>>>>> Ah, I see, thanks.  Although the results is still somewhat
>>>>> unexpected.  c("One:", "Two:") doesn’t have rownames and colnames.  So
>>>>> org apparently made them up when generating the table.
>>>>
>>>> Also expected due to :rownames yes :colnames yes.  Without those two
>>>> header arguments:
>>>>
>>>
>>> Consider this example:
>>>
>>> #+BEGIN_SRC R :results table :exports results :colnames yes :rownames yes
>>>   v <- c("a", "b")
>>> #+END_SRC
>>>
>>> #+RESULTS:
>>> |   | x |
>>> |---+---|
>>> | 1 | a |
>>> | 2 | b |
>>>
>>> Where is the “x” coming from?  In R, colnames(v) gives me NULL.
>>
>> rownames(v) is also NULL.
>>
>> You are asking Org mode to produce a table with row and column names
>> from a vector, which lacks rows and columns.  What behavior do you
>> expect?
>
> Almost anything is better than Org showing me values that do not exist
> in the original data.  Empty cells for row and columns names are
> probably the best solution because that would be faithful to the data
> and to the settings (:rownames yes :colnames yes).

AFAICT, the "x" comes from R, not Org. It could also come from the way
Org calls R, but I don't know enough of the latter to tell.

Regards,