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

Sesame

by gerardroche ST3

Open projects and folders commands.

Details

Installs

  • Total 2K
  • Win 768
  • Mac 555
  • Linux 410
Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15
Windows 0 1 2 0 0 0 1 0 1 1 1 0 1 0 2 0 3 1 0 0 0 1 0 0 1 0 1 0 1 2 3 0 1 1 2 0 1 3 0 0 0 2 2 0 0 0
Mac 0 1 0 1 0 0 1 0 0 0 0 0 0 0 0 1 0 0 1 1 0 0 0 1 0 0 0 0 1 1 0 1 0 1 1 0 0 0 0 0 0 0 0 0 0 1
Linux 0 0 1 1 0 0 0 0 1 0 1 1 0 0 0 1 0 0 1 0 0 0 0 0 0 0 1 1 2 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sesame

Downloads

Sublime Text commands to open, add, remove, and switch projects or folders.

For example when you organise your projects:

$ /path/to/projects
├── laravel
│   ├── fortify
│   ├── framework
│   └── passport
├── sublimelsp
│   └── LSP
└── wbond
    ├── package_control
    └── packagecontrol.io

Sesame commands will prompt you:

laravel/fortify
laravel/framework
laravel/passport
sublimelsp/LSP
wbond/package_control
wbond/packagecontrol.io

If a project folder contains a .sublime-project file, it is used when opening the project.

Setup

Set the projects path.

Command Palette → Preferences: Settings

Error: language “jsonl” is not supported
"sesame.path": "~/projects",

Command Palette

Name Description
Sesame: Open Open project or open folder.
Sesame: Add Add project or add folder.
Sesame: Remove Remove folder from window.
Sesame: Switch Switch to project or folder.

Key Bindings

One key binding is defined by default.

Command Linux / Win Mac
Sesame: Open ctrl + alt + o super + alt + o

Create your preferred key bindings.

Command Palette → Preferences: Key Bindings

Linux / Win

Error: language “jsonl” is not supported
[
    { "keys": ["ctrl+alt+o"], "command": "sesame_open" },
    { "keys": ["ctrl+alt+a"], "command": "sesame_add" },
    { "keys": ["ctrl+alt+r"], "command": "sesame_remove" },
    { "keys": ["ctrl+alt+s"], "command": "sesame_switch" }
]

Mac

Error: language “jsonl” is not supported
[
    { "keys": ["super+alt+o"], "command": "sesame_open" },
    { "keys": ["super+alt+a"], "command": "sesame_add" },
    { "keys": ["super+alt+r"], "command": "sesame_remove" },
    { "keys": ["super+alt+s"], "command": "sesame_switch" }
]

Settings

sesame.path

  • Type: string|list
  • Required

The location of projects.

Placeholders like ~ and environment variables are expanded.

Error: language “jsonl” is not supported
"sesame.path": "~/projects"

Multiple paths

Error: language “jsonl” is not supported
"sesame.path": ["~/projects", "~/vendor", "~/other"]

A list of paths with specific settings for each path.

Error: language “jsonl” is not supported
"sesame.path": [
    {
        "path": "~/projects",
        "depth": 1
    },
    {
        "path": "~/vendor",
        "vcs": true
    }
]

sesame.depth

  • Type: integer (1 | 2)
  • Default: 2

By default, Sesame looks two levels deep inside the path. This maps nicely to vendor/name, which is typical on services like GitHub. For example, when you organise your projects like this:

❯ ~/projects
├── laravel
│   ├── fortify
│   ├── framework
│   └── passport
├── sublimelsp
│   └── LSP
└── wbond
    ├── package_control
    └── packagecontrol.io

Sesame will prompt you with this:

laravel/fortify
laravel/framework
laravel/passport
sublimelsp/LSP
wbond/package_control
wbond/packagecontrol.io

When setting the depth to 1, Sesame will prompt you with this:

laravel
sublimelsp
wbond

sesame.keymaps

  • Type: boolean
  • Default: true

Enable default key bindings.

sesame.vcs

  • Type: null|boolean
  • Default: null

The sesame.vcs setting allows you to control the inclusion of version control system projects. Here are the available options:

  • null: This setting includes both version-controlled and non-version-controlled projects. Projects with and without vcs integration will be considered.

  • true: With this setting, only version-controlled projects will be included. Projects without vcs integration will be excluded.

  • false: This setting excludes version-controlled projects. Only projects without vcs integration will be considered.

Custom commands

Sesame commands accept path, depth, and vcs arguments.

Example

Packages/User/Default.sublime-commands

[
    {
        "caption": "Sesame: Add Vendor",
        "command": "sesame_add",
        "args": { "path": "~/vendor" }
    },
    {
        "caption": "Sesame: Open Vendor",
        "command": "sesame_open",
        "args": { "path": "~/vendor" }
    },
    {
        "caption": "Sesame: Switch Vendor",
        "command": "sesame_switch",
        "args": { "path": "~/vendor" }
    },
]

There is no need to create a custom command for Sesame: Remove because that command prompts with the currently open projects and folders.

Installation

Package Control installation

  1. Open the Command Palette: Ctrl+Shift+P (Linux / Win) or Cmd+Shift+P (Mac).
  2. Type “Package Control: Install Package” and press Enter.
  3. In the input field, type “Sesame” and select it from the list of available packages.

Manual Git installation

  1. Navigate to the Sublime Text Packages directory: Linux “ ~/.config/sublime-text/Packages
Mac

~/Library/Application Support/Sublime Text/Packages

Windows

%APPDATA%\Sublime Text\Packages

1. Clone directly into the Packages directory:
   ```bash
   git clone https://github.com/gerardroche/sublime-sesame.git Sesame

License

Released under the GPL-3.0-or-later License.