I see. So you don't send code to the remote buffer? Copy and paste?

Wonder how easy/hard it would be to make the send code commands work. Would
adding the SAS interactive buffer to the list of ESS processes be
sufficient?
On Jun 13, 2013 7:53 AM, "Rodney Sparapani" <rsparapa@mcw.edu> wrote:

> On 06/13/2013 09:42 AM, Vinh Nguyen wrote:
>
>> Rodney,
>>
>> I tried this before. When I send code via c-c c-r, it starts up an
>> interactive session on my local machine. The inferior SAS buffer from
>> the remote machine doesn't seem to be recognized as an ESS process (not
>> seen in ess-switch-process). Thoughts?
>>
>>
> The `ess-sas-interactive' function was more of a proof of concept.
> Whatever you type in *shell*/*iESS[SAS]* buffer is executed by
> SAS.  There are no bells or whistles.  Patches welcome ;o)
>
> But, honestly, I don't use SAS interactively and I really don't
> know anybody who does with ESS; usually interactive users just
> use Display Manager (but this could be why ;o)  So, we haven't
> invested much effort in this beyond just getting it to work.
> `ess-sas-interactive' depends on fairly low-level ESS/emacs
> functionality so, in theory, it will always work.  But, it might
> not be much fun to use.
>
> --
> Rodney Sparapani, PhD  Center for Patient Care and Outcomes Research
> Sr. Biostatistician               http://www.mcw.edu/pcor
> 4 wheels good, 2 wheels better!   Medical College of Wisconsin (MCW)
> WWLD?:  What Would Lombardi Do?   Milwaukee, WI, USA
>

	[[alternative HTML version deleted]]

