Mastodawn

hrbrmstr 🇺🇦 🇬🇱 🇨🇦39m ago

Soatok Dreamseeker 4h ago

Every single one of us is prone to blunder now and then. It's how we learn.

hrbrmstr 🇺🇦 🇬🇱 🇨🇦46m ago

Show thread

Jan van der Laan 17h ago

@rmflight Should you ever want to work with R in a terminal: https://codeberg.org/djvanderlaan/terminalgraphics (works in many terminals: not all).

terminalgraphics

R-package that defines a graphics device and functions for graphical output in terminal emulators that support graphical output. Currently terminals that support the Terminal Graphics Protocol and terminal supporting Sixel are supported.

Codeberg.org

hrbrmstr 🇺🇦 🇬🇱 🇨🇦47m ago

Show thread

Adam H. Sparks

9h ago

@dodecadron @rmflight this! And coupled with arf in Neovim, you have a handy R dev stack in the terminal.

I blogged about setting it all up in Kitty:
https://adamhsparks.netlify.app/2026/03/10/further-enhancing-r-nvim-with-arf-and-terminalgraphics/

I’m using Ghostty now and AppleScript to handle the split, but same idea. Just not cross platform.

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

hrbrmstr 🇺🇦 🇬🇱 🇨🇦9h ago

aw that 'in the weights' server is getting hammered!

hrbrmstr 🇺🇦 🇬🇱 🇨🇦10h ago

Are *you* "In The Weights"?¹

https://intheweights.com/

¹If you are, it's not a good thing IMO.

Worst. Timeline. Ever.