A maybe less known feature of sublime are the projects. A project is basically the list of open folders and some associated settings. If you start up sublime, then you always have a project open; if you want to save it, open the command palette (ctrl+shift+p or cmd+shift+p by default) chose “Project: Save As” and save it. Sublime saves projects as JSON-files with the descriptive ending “.sublime-project” and further puts a “.sublime-workspace” next to the project file.

The fun comes, when you have more than one project: You can switch between projects by pressing ctrl+alt+p or cmd+ctrl+p. When you switch from project A to B, then A’s open files are stored and B’s open files are recovered, including scroll offset, cursor position, text selection,…, so you can start over where you left. Further you can add custom settings per project, which is handy if you for example have a project where the convention is to use tabs and another project with two spaces.

For a LaTeX involving project I like to use the project settings (“Project: Edit Project”) for ignoring all compile artifacts. LaTeX generates a couple of files, e.g. .aux and .out and I don’t want them to be shown in the file list. This can be done by such a project file:

            "path": "somepath",
            "file_exclude_patterns": [

For viewing the compiled PDF, you can install the plugin Non Text Files and add this to the project settings:

    "settings": {
        "open_externally_patterns": [

This way, sublime does not show you the binary of the PDF, but opens the default application.

This is obviously open to changes, which depend on your project. More on the project settings can be found here and here, happy hacking.