Date: Mon, 1 May 2000 09:32:08 -0400
Reply-To: Scott Chapal <schapal@MAIL.JONESCTR.ORG>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Scott Chapal <schapal@MAIL.JONESCTR.ORG>
Organization: J.W. Jones Ecological Research Center
Subject: Re: Save, Save, Save, Save...
Content-Type: text/plain; charset=US-ASCII.
> > >In UNIX:
> > >
> > >sas -editcmd /usr/bin/vi
> > >sas -editcmd /usr/local/bin/emacs
> > >
> > >Or the inverse - launch SAS from emacs [ESS]:
> > I've tried the above UNIX command, but it doesn't seem to work. Even if it
> > did, wouldn't you still need the SAS program editor to submit the job? Seems
> > simpler to just run vi or emacs from UNIX and submit batch jobs to SAS.
It often is. But for program development or debugging, this works great.
> You need to use a different version of the editcmd invocation for vi in
> an X Windows environment, unless you're using an X-aware vi clone such
> as vim.
If you launch sas from a terminal with the above syntax then that
terminal becomes the edit window. Contents of the program editor are
written to a temporary edit buffer [Invoked with the syntax hostedit
or hed]...when edits are saved the program editor is updated. This
can be done in or out of X. For a non-X session:
sas -fsdevice ascii -editcmd vi
sas -fsdevicd ascii -editcmd emacs
sas -fsdevice ascii -editcmd 'xemacs -nw'
This works in Version 8 despite claims to the contrary.
> The full editcmd is specified in the SAS companion for the Unix
> environment, and requires invoking a terminal from which to run the
> editor in. Something like:
> sas -editcmd <terminal> -e /usr/bin/vi
The reason for doing this is to retain a familiar editing environment.
SAS programs are not the only thing I edit. In my case, emacs
provides a consistent environment for programming, email, usenet, writing
docs etc. The SAS Editor works but only for SAS. I don't need that.