Unable to run SAS code cells within Positron

[rlechtenberg]

Am finding that, unlike in RStudio where SAS code chunks are executable (i.e., the "Run Current Chunk" button shows in the upper right), SAS code cells don't seem to be executable in Positron--even after running library(sasquatch) in a cell above to attach the sasquatch package to the R session--as reflected by the lack of the "Run Cell" and "Run Next Cell" buttons above SAS code cells (see screenshot). In fact, if I click "Run next cell" to run an R code cell immediately before a SAS code cell, Positron seems to jump over the SAS code cell and run the R code cell after it. Any tips? I'd happily simply use sasquatch within RStudio but am wanting to use it within Positron in order to leverage the functionality the SAS Language extension offers for SAS code development (esp. code completion, snippets, syntax highlighting and help)--hopefully possible within SAS code cells in Quarto documents once Positron starts to "recognize" them? This question admittedly may fall outside the scope of this package, but I thought it might be a good place to start, and I'd appreciate any tips you might have!

Also: thanks so much for your work on this package! My colleagues and I are (very regrettably, I'd say) far too invested in SAS at this point to make a clean break with it, and this package feels like a promising tool to facilitate integration of R into workflows still very much rooted in SAS.

[ryanzomorrodi]

I understand your frustrations. Unfortunately, Positron doesn't recognize custom knitr engines. I already opened an issue to add support for sas jupyter kernel (not sasquatch) in quarto. This would benefit sasquatch users as well because then you would get syntax highlighting and code completion as well.

I'm not a typescript dev so I don't feel super confident I could make the PR myself. I did recently make a PR to Positron so maybe I'll mess around on a weekend and see if I can scramble together enough typescript to make a PR.

I'm pretty sure there's a setting somewhere that stops your cursor from moving at all when running a code chunk. That would stop the skipping over the sas code, but is probably annoying in its own way. I use vim keybindings so its not that difficult for me to just highlight the R code and then ctrl+enter, but thats also a way to stop the cursor from moving.

PS: you can see more about this here #15