Re: na=\"nil\" in ob-R.elo

2021-02-06 Thread Jeremie Juste
Hello, Thanks again for reporting this. With the attached patch I'll remove nil replacement for NA. >From 90881079d431a8af3cba5be14ecf882735ed7a6a Mon Sep 17 00:00:00 2001 From: Jeremie Juste Date: Sat, 6 Feb 2021 20:50:00 +0100 Subject: [PATCH] For :results value, return empty string instead

Re: na=\"nil\" in ob-R.elo

2021-01-17 Thread Brett Presnell
I can verify that the :post work-around suggested by Chuck and implemented by Jeremie works as advertised. FWIW, I would certainly prefer to see the implementation org-babel-R-write-object-command changed so that the work-around wouldn't be necessary. Thank you to both Chuck and Jeremie for

Re: na=\"nil\" in ob-R.elo

2021-01-16 Thread Jeremie Juste
Hello, Thanks for the feedback || On Saturday, 16 Jan 2021 at 00:19, Berry, Charles" via "General discussions about Org-mode. wrote: > You can use a :post header to customize outputs like this to make them > more pleasing. Or just use your own > `org-babel-R-write-object-command'. As a

Re: na=\"nil\" in ob-R.elo

2021-01-15 Thread Berry, Charles
> On Jan 14, 2021, at 3:42 PM, Brett Presnell wrote: > > > Probably a silly question, but in ob-R.el, what is the reason for > setting na=\"nil\" when defining org-babel-R-write-object-command? Is > this an elisp compatibility thing? > I don't get it either. The value corresponding to the