'Documentation is a love letter that you write to your future self.' - Damian Conway

8 minute read - Configs

Sublime Text 3 Config

Github Link

Setting up Sublime Text

I have moved from Atom to Sublime. Atom is a nice editor with a lot of features but it has a lot of performance issues for what I want to do.

Below is my setup for reference. When I want to do it again in a year (or a new machine) I can just use everything here or just use the config files.

Install Package Control

Install package control using:

Install Packages

Now you can install packages.

  1. Press Ctrl+Shift+P to open the command palette.
  2. Type Install and then select Package Control: Install Package.
  3. Type the name of the package you are looking for to search for it.
  4. Select the package and press Enter.

Markdown Packages

  1. Markdown Extended: Syntax highlighting.
  2. Markdown Preview.
  3. Markdown Editing: Shortcut keys (e.g. ctrl+1 means heading 1).
  4. Monokai Extended: Need this for the highlighting.
  5. LiveReload: For live markdown preview.
  6. MarkdownTOC: Automatically generate clickable table of contents to markdown documents.
  7. TOML: TOML highlighting.

How to Use the Config Files

After installing packages, just copy the config files to the user package settings directory. On Windows it will be "%Appdata%\Sublime Text 3\Packages\User\" (don't forget the double quotes if you want to just paste it into the run prompt).

Package Settings and Locations

Generally sublime and each package have two types of settings, default and user. User settings are used to override default ones. Both are in JSON.

Settings can be opened via Preferences > Package Settings > Settings Default/User. I usually copy from default file to user, remove the unneeded settings and override the rest.

Package settings on Windows are at %Appdata%\Sublime Text 3\Packages\User\package-name.sublime-settings.

Main settings can be overridden in Preferences.sublime-settings or accessed via Preferences > Settings. This will open two files in one window. Left are the defaults settings and right is the user settings file. Copy from left pane to the right one and override.

Markdown Highlighting and Spell Check

Markdown Editing has its own color scheme. I don't like it. Instead I use Monokai Extended. It can be selected from Preferences > Color Scheme > Monokai Extended > Monokai Extended.

In order for it to kick in, the document type need to be set to Markdown Extended. This can be set by clicking on document type (bottom right).

Next you want to set all markdown files to be opened as Markdown Extended for syntax highlighting (including code blocks). This can be done by:

  • View (menu) > Syntax > Open all with current extension as > Markdown Extended.

This method only sets it for the current extension (e.g. md).

Go to Preferences > Settings - Syntax Specific or edit package settings Markdown Extended.sublime-settings and add the following:

  "spell_check": true // enable spell check

Note that Markdown Editing has added itself for .mdown files. You can just delete the file Markdown.sublime-settings and add the extensions in the previous file.

Setting up Markdown Live Preview

Enable LiveReload via Settings

Add the following to user settings for the LiveReload package LiveReload.sublime-settings:

  "enabled_plugins": [
   "SimpleRefreshDelay" // use SimpleRefresh for reload without delay

This way it does not need to be re-enabled after every start.

Enable LiveReload Manually (repeat after every Sublime launch)

  1. Open command palette and type livereload.
  2. Select LiveReload: Enable/disable plug-ins.
  3. Select Enable - Simple Reload with delay(400ms).
  4. You should see a console message saying it was enabled. Note that the menu will say Enable whether it's enabled or not, if it's already enabled choosing the menu will disable it so make sure to look at the console messages.

Configure Markdown Preview

Supposedly these two plugins work out of the box. It was not in my case. I had to add autoreload in markdown preview. I removed the github parser because it sends the markdown file to Github to be processed.

Add the following to MarkdownPreview.sublime-settings:

  "enable_autoreload": true,
  "enabled_parsers": ["markdown"],
  "enable_highlight": true

Preview Files

  1. Open command palette and select Markdown Preview: Preview in Browser.
  2. A new browser window will open to display the rendered document.
  3. Browser should update after every save.

Preview Keybind

Add the following to Default (Windows).sublime-keymap or open it via Preferences > Key Bindings.

  "keys": [
  "command": "markdown_preview",
  "args": {
    "target": "browser",
    "parser": "markdown"

Markdown Table of Content

  1. Install package Markdown TOC.
  2. Add the following user settings to MarkdownTOC.sublime-settings:
  "defaults": {
    "autoanchor": true,
    "autolink": true,
  1. In any markdown document, put the cursor where you want the T0C. Then Tools > MarkdownTOC > Insert TOC.
  2. All settings can also be controlled in the T0C by adding them to the top comment. For example:
<!-- MarkdownTOC style="round" autolink="true" depth=0 -->

- [Heading 1]
- [Heading 2]

<!-- /MarkdownTOC -->

TOC Keybind

Add the following to the keymap Default (Windows).sublime-keymap:

  "keys": [
  "command": "markdowntoc_insert"  // update is markdowntoc_update

Change Bold and Italic Markers

By default in markdown editing, bold marker is __ and italic is _. I am more used to ** for bold and * for italic.

Simply add a file named Bold and Italic Markers.tmPreferences and put it in the usual User directory.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "">
<plist version="1.0">
  <string>Bold and Italic Markers</string>

Snippets vs. Completions

Essentially both do the same.

  1. Snippets are XML while Completions are JSON.
  2. Snippets are easier to read because you can have new lines in CDATA tags while you have to escape doublequotes and use special characters for new lines (e.g. \n).
  3. Only one snippet is allowed per file while you can have multiple completions in one file.

Mainly as a result of 3, I went with completions because it's just one file and easier to manage (although harder to read).


Tools > Developer > New Snippet will create and open a template. Files are stored in the User directory similar to config files (although packages can have their own snippets). Extension for snippets is sublime-snippet.

Unofficial documentation page:

Actual snippet is in the content tag which supports new lines inside CDATA.

For example the Snippet for my Hugo shortcode codecaption (link) (remove the /*s).

  <content><![CDATA[{{< codecaption title="$1" lang="$2" >}}
${3:default text}
{{</* /codecaption >}}
  <!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
  <!-- Optional: Set a scope to limit where the snippet will trigger -->
  <!-- Optional: Description to show in the menu -->
  <description>Codecaption Hugo Shortcode</description>

$1 means the cursor will be there after the snippet is activated, after typing and pressing tab we will jump to $2. $3 has a default text which will be highlighted after cursor jumps to it and can be overwritten.

scopeis where the snippet will be active. Without a scope, it's active in all documents. To get the current scope press ctrl+alt+shift+p or through Tools > Developer > Show Scope Name.

Same thing can be done for imgcaption (link) (remove the / *, * /s).

  <content><![CDATA[{{</* imgcap title="$1" src="/images/2017/${2:imagepath}" >}}]]></content>
  <!-- Optional: Set a tabTrigger to define how to trigger the snippet -->
  <!-- Optional: Set a scope to limit where the snippet will trigger -->
  <!-- Optional: Description to show in the menu -->
  <description>Imagecaption Hugo Shortcode</description>


I prefer completions because all can be in one file. For most purposes we can treat them like snippets. They are JSON files so escape " with \" and new line is \n.

Link to unofficial wiki:

Completions are stored in the User directory with extension .sublime-completions.

Sample completion file for markdown for the same shortcodes. Note the triggers are the same as the ones in snippet examples above. Snippets always have priority over completions.

   "scope": "text.html.markdown - source - meta.tag, punctuation.definition.tag.begin",

      { "trigger": "codecap\tCodecaption Hugo Shortcode", "contents": "{{< codecaption title=\"$1\" lang=\"$2\" >}}\n${3:default text}\n{{< /codecaption >}}" },
      { "trigger": "imgcap\tImagecaption Hugo Shortcode", "contents": "{{< imgcap title=\"$1\" src=\"/images/2017/${2:1.png}\" >}}" }

Note the trigger, the first part is the actual trigger and everything after \t is the hint that appears in the autocompletion list similar to snippet descriptions.

There are tons of completion files for different languages and frameworks online and in package control.

Snippet and Completion Triggers

In short type the trigger (or parts of it if it's unique) and press tab. If there are snippets and completions with the same triggers, snippets always have priority.

  • Typing codecap and pressing tab will activate the snippet/completion.
  • Typing code and ctrl+space will show it in the auto-complete menu.
  • Typing snippet in the command palette will show all snippets for the current scope along with their triggers.

Fix "MarGo build failed" for GoSublime on Windows

GoSublime's executable has Go version in it. In most cases, it cannot grab the version on Windows and the build will fail like this:

MarGo: MarGo build failed
cmd: `['C:\\Go\\bin\\go.exe', 'build', '-tags', '', '-v', '-o', 
       'gosublime.margo_r17.12.17-1_go?.exe', 'gosublime/cmd/margo']`

Where ? is the go version that is unknown.

Edit this file:

  • %AppData%\Sublime Text 3\Packages\GoSublime\gosubl\

Find these lines:

cmd = ShellCommand('go run sh-bootstrap.go')
cmd.wd = gs.dist_path('gosubl')
cr =
raw_ver = ''
ver = ''     # Edit this to '1'

Edit ver to whatever, I usually do 1. Restart Sublime Text and Margo will build.

Unfortunately this needs to be done for every new GoSublime version.