From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Brett Presnell <presnell@member.fsf.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: na=\"nil\" in ob-R.elo
Date: Sat, 16 Jan 2021 00:19:05 +0000 [thread overview]
Message-ID: <97F6B6F8-E109-4089-8C21-03E087AA4AD3@health.ucsd.edu> (raw)
In-Reply-To: <87h7njdr0x.fsf@ufl.edu>
> On Jan 14, 2021, at 3:42 PM, Brett Presnell <presnell@member.fsf.org> 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 NA becomes a string in emacs-lisp whether \"nil\" or \"\" is used.
So when passed to elisp via a :post header referencing an emacs-lisp src block, its treated as a string.
> Regardless, I generally (always?) want na=\"\" for this, so I am finding
> all those "nil"s very annoying, and the only way that I see to defeat
> them is to redefine org-babel-R-write-object-command.
>
> If there is no reason for the current behavior (doubtful I know) and if
> I am not missing an obvious work-around, then I would like to suggest
> changing this behavior. Otherwise, would it be feasible to add an
> option for R code blocks (:nastring?) where one could specify the NA
> replacement string?
>
> What do you think? It's easy to suggest I know and certainly beyond my
> elisp coding skills at present, but I am supposing that someone more
> fluent in elisp could do this safely without too much trouble.
>
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'.
Adding another header arg qualifies as feature creep and in this case would require non-trivial work to implement.
HTH,
Chuck
next prev parent reply other threads:[~2021-01-16 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 23:42 Brett Presnell
2021-01-16 0:19 ` Berry, Charles via General discussions about Org-mode. [this message]
2021-01-16 13:35 ` Jeremie Juste
2021-01-17 21:48 ` Brett Presnell
2021-02-06 20:05 ` Jeremie Juste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97F6B6F8-E109-4089-8C21-03E087AA4AD3@health.ucsd.edu \
--to=emacs-orgmode@gnu.org \
--cc=ccberry@health.ucsd.edu \
--cc=presnell@member.fsf.org \
--subject='Re: na=\"nil\" in ob-R.elo' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).