xeus-r
xeus-r copied to clipboard
jupyter-xeus
Jupyter kernel for the R programming language
https://github.com/jupyter/jupyter_kernel_test/blob/55e33601f4ab3ca4c7ac45ddc4c538b2769c3f68/jupyter_kernel_test/__init__.py#L308 ```python def test_history(self) -> None: if not self.code_execute_result: raise SkipTest("No code execute result") # noqa codes = [s["code"] for s in self.code_execute_result] _ = [s.get("result", "") for s in...
Not sure what `user_expressions =` is
As of #61, we have the `log_debug()`, `log_info()` and `log_info()` functions on the R side that end up calling `xeusr_log()` which at the moment does not do much of anything:...
Right now (as of #59), we handle history with a `xeus::make_in_memory_history_manager()` but this sort of bypass the way R would usually deal with history, which would e.g. give access to...
Follow up on https://github.com/conda-forge/staged-recipes/pull/24469#discussion_r1390251186
Paging
Not sure what to do with paging just yet. The default test has: ```py # code_page_something = "?cat" ```
Currently the supporting R code is loaded, in `interpreter::configure_impl()` from a directory based on where `xr` is: ```cpp void interpreter::configure_impl() { SEXP sym_Sys_which = Rf_install("Sys.which"); SEXP sym_dirname = Rf_install("dirname"); SEXP...
Currently the kernel does not work on windows, because e.g. the "Rinterface.h" file is not available on windows. We use this file for e.g. `ptr_R_WriteConsoleEx`. The callbacks are implemented differently...