Mastodawn

@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

Split ghostty window with AppleScript · 9a28fbbce1

New option: external_term = "ghostty_split" use AppleScript to split the Ghostty terminal window.

Codeberg.org

Adam H. Sparks

Mar 15

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

Further Enhancing R.nvim with arf and {terminalgraphics}

TLDR Pass the shell’s PATH along to the kitten (split) via kitty’s config file. Kitty launches the kitten (for the split) using a minimum configuration that doesn’t see your $HOME/.cargo/bin (where arf lives) and won’t pick up the rig installation that arf looks for. Here are the lines in my config files that make this happen. $HOME/.config/kitt/kitty.conf environment, R.nvim, also see: https://github.com/R-nvim/R.nvim/blob/2d0cd152800ced779caaba4684a42efae81203b5/doc/R.nvim.txt#L1168. $HOME/.config/nvim/lua/plugins/r-nvim.lua. R_app, external_term. Updated 2026.05.11 I refined my config files and have a better understanding of the issues with trying to use the arf console in an R.

Adam H. Sparks

Zhian N. Kamvar Aug 9, 2024

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

I was thinking to switch over to #VScode or #positron, but having to learn new shortcuts for everything make me sad.

Highlight ROxygen tags · Issue #68 · r-lib/tree-sitter-r

Are ROxygen tag highlighting something that can be added? With treesitter disabled they get highlighted from the main neovim runtime: https://github.com/neovim/neovim/blob/c651a0f643e7bd34eb740069a...

GitHub