For using SAS Institute's Analytics & Data Management system.
- Total 4K
- Win 3K
- Mac 781
- Linux 259
|May 31||May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19||Apr 18||Apr 17|
SAS Programming Package for Sublime Text 3
A modest package for doing SAS programming.
Syntax definitions (highlighting) for SAS Programs and .log files. A build system that 1. Batch-submits the currently-showing program to your local install of SAS. 2. Waits for said program to finish. 3. Opens the resulting .log file and checks it for errors or warnings (via a user-configurable regular expression). A macro (bound to ctrl-e) for jumping from error/warning to error/warning in your log.
Snippets! 1. 'sql' starts up a proc sql - quit block. 2. 'mac' creates the shell of a macro. 3. 'mloop' creates a shell macro that loops through all the vars in a dataset (saving you from having to remember where to put the double-ampersands). 4. 'frq' starts up a FREQ call. 5. 'srt' starts up a SORT call. 5. 'tp' starts up a TRANSPOSE call. 7. Many more!
Indentation rules. Completions.
Installation is via the wonderful Package Control. Choose 'Package Control: Install Package' off the command palette and then find 'SAS Programming' on the resulting list.
Once that's done, create a trivial sas program (e.g., proc print data = sashelp.class ;), save it to a file (e.g., deleteme.sas) and hit ctrl-b to 'build' (aka batch-submit) your program. One of two things will happen: 1. The package will find your copy of sas.exe in the location it expects, and the program will be batch-submitted (probably 20% of installs). 2. The package will not find sas.exe where it's expected and it will prompt you to tell it where your sas.exe is.
If you get outcome 2 there, use the menus to navigate to Preferences -> Package Settings -> SAS -> Settings-User. That will open up the preferences file. Find and edit the value listed for the “sas-path” at the bottom. Enter the full path to your local copy of sas.exe. Windows users, note that backslash characters need to be escaped (doubled up) to be properly read.
- Polish build system.
- Play a sound at the finish of a job to call attention?
- Distinguish the taskbar icon from ST3's on the dialog that informs users that a build is complete?
- (Possible?) Bring (relevant instance of) ST3 to the fore upon dismissing finish dialog.
- Tap into built-in 'results view' stuff for error/warning navigations.