SAS Programming
For using SAS Institute's Analytics & Data Management system.
Details
Installs
- Total 4K
- Win 3K
- Mac 786
- Linux 259
| Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | Sep 21 | Sep 20 | Sep 19 | Sep 18 | Sep 17 | Sep 16 | Sep 15 | Sep 14 | Sep 13 | Sep 12 | Sep 11 | Sep 10 | Sep 9 | Sep 8 | Sep 7 | Sep 6 | Sep 5 | Sep 4 | Sep 3 | Sep 2 | Sep 1 | Aug 31 | Aug 30 | Aug 29 | Aug 28 | Aug 27 | Aug 26 | Aug 25 | Aug 24 | Aug 23 | Aug 22 | Aug 21 | Aug 20 | Aug 19 | Aug 18 | Aug 17 | Aug 16 | Aug 15 | Aug 14 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 1 | 1 | 0 | 0 | 2 | 1 | 1 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 2 | 1 | 0 | 0 | 2 | 0 | 1 | 0 | 3 | 0 | 0 | 3 | 1 | 0 | 3 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
SAS Programming Package for Sublime Text 3
A modest package for doing SAS programming.
Features
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
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.
To-Do
- 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.