From: Richard A. DeVenezia on
Bill Howells wrote:
> Thanks. I probably did more than is necessary but I copied the main
> sasv9.cfg file to my personal dir, renamed it myconfig.cfg, edited the
> sasuser option to point to my dir, created my own autoexec.sas in my
> dir, then start SAS with
>
> sas -config myconfig.cfg -autoexec myauto.cfg
>
> and sas created profile, registry, and USERPREFS files in my dir. My
> appreciation for SAS has grown!
>
> Now if I can just figure out how to map the "end" key to actually go
> to the end of the line in pgm rather than submit a job. There is no
> "end" key in the DMKEYS file.

There are a large number (a slew) of X RESOURCE variables that allow you to
control many UI aspects of SAS in Unix.

Look in your help file for Unix companion, or online at
http://support.sas.com/91doc/docMainpage.jsp
Contents/Base/Operating Environment/Companion UNIX/Running SAS/Customizing

Happy tweaking!

--
Richard A. DeVenezia
http://www.devenezia.com/


From: Bill Howells on
couple more weird things . . .

I found Resource Helper to define the "end" key to go to the end of a
field (as an "X resource"), but it saved the resources in a file
called "SAS" in the common account dir, so I believe I just defined them
for everyone else. whoops.

my key definitions in DMKEYS are saved.

but . . .

changes to program editor such as AUTOSPLIT=ON are not saved with a new
session.

The SAS companion for UNIX doc is very good so will have to read that
thoroughly to figure out what mess I have made.

Ron, I double checked and I did name my personal autoexec with *.sas, just
mistyped in the post, thanks. Bill H, Wash U, St Louis
From: Richard A. DeVenezia on
Bill Howells wrote:
> couple more weird things . . .
>
> I found Resource Helper to define the "end" key to go to the end of a
> field (as an "X resource"), but it saved the resources in a file
> called "SAS" in the common account dir, so I believe I just defined
> them for everyone else. whoops.
>
> my key definitions in DMKEYS are saved.

They get saved automatically when the KEYS window is ENDed (F3). Changes
might be properly unsaved if you CANcel the KEYs window.

>
> but . . .
> changes to program editor such as AUTOSPLIT=ON are not saved with a
> new session.

Aspects of various need to be WSAVEd. Did you do a WSAVE (or WSAVE ALL)?
wsaving creates WSAVE entries in SASUSER.PROFILE.
Is "automatically save preferences" checked in options ?

FWIW, Nedit.org is a pretty sweet editor for UNIX.

Looking forward to your questions about printing :)

--
Richard A. DeVenezia
http://www.devenezia.com/


From: Bill Howells on
On Tue, 1 May 2007 18:29:36 -0400, Richard A. DeVenezia
<rdevenezia(a)WILDBLUE.NET> wrote:

>Bill Howells wrote:
>> couple more weird things . . .
>>
>> I found Resource Helper to define the "end" key to go to the end of a
>> field (as an "X resource"), but it saved the resources in a file
>> called "SAS" in the common account dir, so I believe I just defined
>> them for everyone else. whoops.
>>
>> my key definitions in DMKEYS are saved.
>
>They get saved automatically when the KEYS window is ENDed (F3). Changes
>might be properly unsaved if you CANcel the KEYs window.
>
>>
>> but . . .
>> changes to program editor such as AUTOSPLIT=ON are not saved with a
>> new session.
>
>Aspects of various need to be WSAVEd. Did you do a WSAVE (or WSAVE ALL)?
>wsaving creates WSAVE entries in SASUSER.PROFILE.
>Is "automatically save preferences" checked in options ?
>
>FWIW, Nedit.org is a pretty sweet editor for UNIX.
>
>Looking forward to your questions about printing :)
>

WSAVE worked, thanks so much!

No kidding on the printing. Fortunately, ods rtf works under UNIX, just
downloaded rtf file and printed in Word. I'm a chicken. :) I do need to
actually get some work done and stop fiddling with the setup. Thanks
again for the help! Bill H.