For using SAS Institute's Analytics & Data Management system.
- Total 3K
- Win 2K
- OS X 611
- Linux 189
|Dec 6||Dec 5||Dec 4||Dec 3||Dec 2||Dec 1||Nov 30||Nov 29||Nov 28||Nov 27||Nov 26||Nov 25||Nov 24||Nov 23||Nov 22||Nov 21||Nov 20||Nov 19||Nov 18||Nov 17||Nov 16||Nov 15||Nov 14||Nov 13||Nov 12||Nov 11||Nov 10||Nov 9||Nov 8||Nov 7||Nov 6||Nov 5||Nov 4||Nov 3||Nov 2||Nov 1||Oct 31||Oct 30||Oct 29||Oct 28||Oct 27||Oct 26||Oct 25||Oct 24||Oct 23||Oct 22|
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.