ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

SAS Programming

For using SAS Institute's Analytics & Data Management system.

Details

Installs

  • Total 3K
  • Win 2K
  • OS X 548
  • Linux 169
Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7
Windows 0 3 3 2 1 1 3 4 1 4 2 0 0 2 0 1 2 1 0 0 2 1 1 1 4 0 1 2 8 2 3 4 1 0 1 1 1 4 1 0 0 0 0 0 2 2
OS X 0 2 0 0 0 0 0 0 0 1 0 0 0 0 0 1 2 0 0 0 1 0 0 0 0 1 0 0 0 1 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 1 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

  1. Polish build system.
    1. Play a sound at the finish of a job to call attention?
    2. Distinguish the taskbar icon from ST3's on the dialog that informs users that a build is complete?
    3. (Possible?) Bring (relevant instance of) ST3 to the fore upon dismissing finish dialog.
    4. Tap into built-in 'results view' stuff for error/warning navigations.