And it was a bug that the ob-core patch fixed. Unfortunately, a number of babel backends also developed workarounds meanwhile. For the context, the ground truth is Org manual: 16.4 Environment of a C
given that, iiuc, 9.5 presented a list as (the equivalent of) multiple rows of a table, i'd vote for staying with (going back to) that. (i think that's what the two modifications in Chuck's e-mail g
Jeremie, i am neutral w.r.t. what the output should be. like you, i've always sent in tables. for me, i don't know that it makes much difference how lists are presented to R code, as long as it is we
Hello, Many thanks for the insights. I confess that I have never transferred list from org to R before. I've always use tables and as far as I understand they works fine in 9.6. So assuming this list
[snipped] Yeah, the problem is not a change to ob-R.el but the recent change to ob-core.el (see the message of the commit I referenced). But the change to ob-core.el is final if I understand it corre
i see this same behavior. to me, (org-babel-R-assign-elisp) seems to be the problem, but it hasn't changed any time recently. (nor, if my =git blame= is done correctly, has anything else in ob-R.el.)
for the record, these are the tests i ran with my off-the-cuff "fix" (s/sequencep/listp/): -- - first item - second item - third item list variable list list list
i see this same behavior. to me, (org-babel-R-assign-elisp) seems to be the problem, but it hasn't changed any time recently. (nor, if my =git blame= is done correctly, has anything else in ob-R.el.)
After the changes to ob-core.el introduced in commit: b4e437f968771df9555f9306467846965857f632 plain lists passed to R source code blocks are generated with extra (empty) items. Example: - first item
Thanks! Should be fine I think. We have a mess with spaces and tabs in some places. Applied onto main with amendments. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2e012db31a8dbae0
I'm attaching the patch for the current approach we discussed in this thread. I have tried basic operations like taking note on state change, and have tried with recurring entries which need more tha
You do not need to share the paperwork with us. FSF has a database available to GNU maintainers with a list of all the people with copyright assignment. I am CCing Bastien. Bastien, can you please co
I finally got this done. I now have a fully executed copy of the copyright assignment (signed by FSF and me). Do I need to send it to someone so that they can check and update the page at https://org
Yikes! Then, can also check for window-minibuffer-p, but I feel that it will be a fight against all kinds of edge cases. what about (when (or (and (equal org-log-note-this-command this-command) (= or
Thanks! I received the PDF to sign the next day after my email, this will probably take a couple of days more from my side as I'm talking with my employer. So, I saved this-command and (recursion-dep
Thanks for the idea, I'm exploring (recursion-depth), (minibuffer-depth). I will come up with a patch to fix this bug. Seems like soon I will cross the TINYCHANGE limit, so I will get the FSF copyrig