you don't need to copy/paste from that preview! the rendered reprex, in a friendly md form, is already on your clipboard 😆

the htmlpreview is for your 👀, but the good stuff is on the clipboard waiting to be pasted in the relevant venue (default is github, but slack can also be requested)

the tidyr::separate_wider_*() functions might offer a nice little improvement to your existing approach

this idea has been kicking around for years and @henrikbengtsson.bsky.social catalyzed something at an rOpenSci unconf once: github.com/HenrikBengts...

Vignette workflows are just inherently awkward since, unlike help topics and `man/*.Rd` files, the rendered form of vignettes has no legit business or home inside an R package in source form. This chapter outlines some of the least bad workflows:

r-pkgs.org/vignettes.html

I define short aliases `bp()` and `bg()` for `usethis::browse_package()` and `usethis::browse_github()` in `.Rprofile` because I use them so much.

maybe it should be your first Pythong package 🩴

I still marvel at the choice to do "C:\Program Files"

this is a *wild* exaggeration but I'll allow it 🤣

2️⃣ I HAVE SUCH STRONG FEELINGS ABOUT THIS but already sense that it's a lost cause

I'd install Xcode command line tools (NOT all of Xcode) to get git and compilers, etc. (xcode-select --install)

and I'd use rig to install one or more versions of R (github.com/r-lib/rig)

(my macbook's logic board failed and is being replaced, so I'll be doing all this set up myself soon 😬)

enough women to make a line 😄