Sublime Text 3 plugin that adds support for Stata (all versions) in Linux.
- Total 64
- Win 0
- Mac 0
- Linux 64
|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||Apr 16||Apr 15|
Sublime Text 3 plugin that adds basic support for Stata (all versions) in Linux.
- Language definitions for
- Commands for sending a selection of lines or the whole file to Stata. See usage for more details.
I needed a minimal yet robust plugin for sending code from Sublime Text into Stata. Since none of the plugins in the Package Control was specifically tailored for Linux, and none of the maintainers seem to want to add Linux support to theirs, I wrote my own. This plugin is originally based on StataEnhanced, and also on these notes.
This plugin aims for robustness over bells and whistles, and almost all the decisions were taken with that philosophy in mind.
It basically creates a temporary file which is to be executed in Stata.
The file is sent for execution by copying
do <filepath> to the clipboard with
xclip, and then pasting this string directly (and in the background) to Stata's command pane using
These packages are likely already in your system.
You can check their presence by typing each name with the
--version option in your terminal.
If the output is something like
xdotool version 3.20160805.1, then it's installed.
If you get an error, then the package is not installed.
Use your system's package manager to install them.
sudo pacman -S xclip xdotool
sudo apt install xclip xdotool
There are two ways to install this plugin:
- Search for “StataLinux” on Package Control, or
- Copy/clone the entire plugin folder (this repository) to
Make sure you have installed the dependencies listed above before using it.
Make sure you have one instance of Stata open.
.ado) file in ST3.
You have two keybindings for executing code:
ctrl+alt+dexecutes the current line, or the selected lines if a selection is made, and
crtl+alt+shift+dexecutes the entire file.
These actions may also be called using the Command Palette: after invoking it with
ctrl+shit+p, type “StataLinux” and select an action.
Additionally, these actions are accessible in the main menu under
Tools > Packages > StataLinux.
Note that if a line is only partially selected, the program will automatically select the whole line for execution. Also, when sending the whole file for execution, StataLinux will default to saving the current file first. This option can be disabled in the settings.
Comment toggling for entire lines works with the default ST3 keybinding,
Arbitary blocks can be commented out with
Typing a backtick
` anywhere in the code will immediately put a closing tick after it, with the cursor inside.
Typing a backtick with a
word selected will yield
Stata versions, flavors and instances
Make sure you have an instance of Stata with GUI open (
xstata, or its various flavors); this plugin doesn't work with Stata's CLI.
No additional configuration needs to be added to indicate version or flavor, since the program will detect any running instance automatically.
If you have more than one instance of Stata open, the plugin will default to choosing the most recently opened one (internally, it looks for the last entry of
xdotool search --classname "stata").
Currently, there is an issue withNow not an issue, since I'm using
clearmodifiersoption. This has the consequence that the plugin will fail to operate correctly if any keyboard modifiers (e.g. Caps Lock) are not manually turned off.
--window, which seems cleaner than focusing and refocusing windows, and has the added bonus of disregarding any active modifiers.
There is currently no option for switching focus to the Stata window. This is because there are good reasons to use
--windowoption (see issue #1), so I don't plan on implementing this. Window focus is a task for window managers, anyway.