>> Additionally, if the variables simply hold R code text, then users can >> easily initialize them from R files locally with something like the >> following. >> >> (setq org-babel-R-assign-elisp-function >> (with-temp-buffer >> (insert-file-contents-literally "personal.R") >> (buffer-string))) >> >> I think this approach is much simpler. > > True - but I like the simplicity of being able to customize the > behavior of org-babel-R by writing an R function without having to thin > about elisp. But maybe there is a way of doing both... >
I guess one man's simplicity is another confusing magic. I don't see the difficulty in having to change the value of an elisp variable, to change the R code executed by an Emacs process, in fact I think this is the most straight forward and expected way to do such customization. > New behavior (environment): > 1) Define the R code in emacs variables, i.e. customizable in emacs. > 2) Define a function to load the code into an R environment - not > customizable. The above sounds good to me. It might be nice to also include a customizable variable which controls whether the function in (2) is run at all. Best, -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
