#rnvim — Public Fediverse posts

@adamhsparks You can find the `ghostty_split` branch here:
https://codeberg.org/gcarlino/R.nvim/commit/9a28fbbce133141dbd04097560fa4513b6c0dc73

It introduces the option `external_term = "ghostty_split“`, leveraging AppleScript in Ghostty. I do not know if there are better ways to do it, not limited to macOS.

Anyway, please keep in mind I did very limited testing since at the moment I am still using httpgd.
Furthermore, I did it with the help of AI (which is a concern to me), but I have fully reviewed and partly rewritten it.

#RNvim #Rstats #ghostty

I've written up a how-to for using arf and {terminalgraphics} in R.nvim. Glad I did. I discovered a few gotchas that I'd forgotten and now have them recorded and cleaned up my nvim config files at the same time.

So, now you can have the IDE console experience in R.nvim AND the graphics baked in, no X11 or {httpgd} windows to fuss with. The only catch is you have to use Kitty or Wezterm for your terminal emulator.

https://adamhsparks.netlify.app/2026/03/10/further-enhancing-r-nvim-with-arf-and-terminalgraphics/ cc @jimbob

#RStats #Neovim #RNvim

Last month I switched over from using #NvimR to #RNvim (the lua-based successor), which uses #TreeSitter for syntax highlighting. It was hard enough to do the transition and the realize that debugging support was turned off, but one of the biggest disappointments is the lack of #roxygen highlighting (https://github.com/r-lib/tree-sitter-r/issues/68), which is actually default in #Nvim :blobfoxcry2: I was thinking to switch over to #VScode or #positron, but having to learn new shortcuts for everything make me sad.