WSL operations work best on the WSL file system, not the windows one, but RStudio doesn't like the WSL file system (various warnings/errors, knitr doesn't work properly, not sure about quarto) because it's represented as some sort of pseudo-network location.
I've identified a few workarounds, but none of them seem ideal:
1. Run RStudio Server inside WSL => the web version is imo a lot more clunky to use than the native desktop version.
2. Use VSCode instead of RStudio and rely on its remote WSL integration like I do for bash/Python projects => RStudio is still king for data wrangling in R.
3. Store everything on the Windows file system => works for projects that are mostly R-based, but less than ideal for multi-language projects. Plus OneDrive tends to freak out when you create git and renv environments this is fine fire
4. Run RStudio directly from WSL through WSLg => performance is supposedly worse? Although this would make multi-language projects easier to work with since everything is residing in WSL.
5. Somehow fix RStudio's dislike of the WSL file path? Wait for Posit to introduce remote/WSL functionality like vscode and Jetbrains IDEs? Use some arcane config setting to make the errors go away?
More context: I mostly work on my Linux partition when I can, but these days I need to do quite a bit of admin work in office 365, and the web experience is sub-par. Combine that with some of the usual linux-jank that you can expect on newer hardware, and I tend to spend quite a bit of my time in Windows.