Jeremie Juste <jeremieju...@gmail.com> writes: > On Thursday, 8 Dec 2022 at 09:07, Ihor Radchenko wrote: > >> I am not sure if I like the approach you used in the commit. >> >> - (unless (listp (car value)) (setq value (list value))) >> + (unless (listp (car value)) (setq value (mapcar 'list value))) >> >> In the above, you are transforming (val1 val2 val3 ...) list into >> ((val1) (val2) (val3) ...). >> >> Does it make sense from the point of view of R code? >> AFAIU, the current ob-R implementation converts lists into R tables, >> which is not accurate? Would it make sense to convert Elisp lists into R >> lists directly? > > Many thanks for the feedback. At this point I don't know. On one hand you are > right on the other, this option is backward compatible, and the user can > always create an interface in R to suit his need. > > If there are more complaints about that in the future, I'll reconsider.
Note that my NEWS entry may not be accurate for ob-R then: ** List references in source block variable assignments are now proper lists So, we may create confusion one way or another. Or I may need to put a special clause regarding ob-R into the NEWS item. Bastien, maybe you have something to say about this situation? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
