Managing editor plug-ins

Package Control supplements and enhances the functionality of Sublime Text. It offers a couple of ways end-users can install and use plug-ins, viz., (a) from the official index list, which requires developers to make an effort to submit theirs, or (b) it allows a package repository to be added directly to Sublime Text without the need to go via the method (a) route. Both these methods are described in Usage. Here is a demo covering both methods.1

Ways to install packages (plug-ins) in Sublime Text.

The two packages sacs_st and usfos_st got developed because I needed syntax highlighting for my model files. I took the time to have them listed, thinking these could readily be useful to others too. Whereas for latex-snippets-st, my other package, I decided not, since Sublime Text is pre-bundled with a good LaTeX package already; my above package supplements it with personalised triggers and snippets. Still the interested can easily install. See the video from 36s onward on how-to.

Vim Plug is a one-line installer, followed by a simple block within .vimrc to download and install the plug-ins of choice. Here is an example using my latex-snippets-vim plug-in.

call plug#begin('~/.vim/plugged')
Plug 'sirver/ultisnips'
Plug 'ckunte/latex-snippets-vim'
call plug#end()

Plug calls GitHub repositories by default. Then all one needs is reload .vimrc and :PlugInstall to install plug-ins. Plug-ins can be updated with :PlugUpdate. Removing plug-ins is also as easy as removing Plug lines from .vimrc, reload, and running :PlugClean from within Vim. See a demo below.2

Updating plug-ins via Vim Plug.

  1. Each method has its benefits. Method (a) offers greater visibility to end-users, while method (b) enables greater control and access to packages that may not be available from Package Control’s global list. ↩

  2. See also Nick’s video commentary regarding Vim Plug. ↩