Let me follow up on my line mode comment. When I was a SAS developer, I did most of my editing in emacs. I developed some emacs commands to write the entire buffer, from the point down, a marked region, or the next step to a file then automatically %include that file in the SAS line mode window. It was like my personal display manager. Now granted, as a SAS developer, my methods of using SAS were different than most users. I would at times enable debugging code, and I always wanted to see those results in amongst the log and output. It worked really well for me, and a number of my colleagues used my emacs tools. As primitive as line mode seems, I found it highly effective when coupled with some SAS-specific editing capabilities.
I used Unix for most of my career, so haven't tried it, but this should be helpful. https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/hostwin/p16esisc4nrd5sn1ps5l6u8f79k6.htm#n1rc...
No. Working in an rscript typically looks like this:
Both the results and the log-messages goes in the console.
Any plots generated are either in side panel or popup-window.
The output of an Rmarkdown is the same, but can also be inline (in the source window), or indeed as a third window when generating the whole Rmarkdown, but this is typically done rarely or at the end of a session.
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.
Find more tutorials on the SAS Users YouTube channel.