ProjectSpecific
Configure project specific commands, keymaps, etc. in your project-file.
Details
Installs
- Total 526
- Win 260
- Mac 162
- Linux 104
| Nov 5 | Nov 4 | Nov 3 | Nov 2 | Nov 1 | Oct 31 | Oct 30 | Oct 29 | Oct 28 | Oct 27 | Oct 26 | Oct 25 | Oct 24 | Oct 23 | Oct 22 | Oct 21 | Oct 20 | Oct 19 | Oct 18 | Oct 17 | Oct 16 | Oct 15 | Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | Oct 6 | Oct 5 | Oct 4 | Oct 3 | Oct 2 | Oct 1 | Sep 30 | Sep 29 | Sep 28 | Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- bitbucket.org
Project-Specific
This extension enables you to add project specific configuration to Sublime Text 2.
Example:
{
"folders": ...
"settings": {
"project-specific": {
"sublime-keymap": [
{"keys": [ "ctrl+B"],
"command": "exec",
"args": ["echo", "my build"]
}
],
"sublime-commands": [
{"caption": "My Command",
"command": "open_file",
"args": {"file": "my file.x"} }
]
"sublime-macro": {
"macro1": [ ... ],
"macro2": [ ... ]
}
}
}
}
Each time you switch to a project, the configuration files in User/Project-Specific will be updated. For example above, there would be created:
- User/Project-Specific/Default.sublime-keymap
- User/Project-Specific/<project-name>.sublime-commands
- User/Project-Specific/<project-name> macro1.sublime-macro
- User/Project-Specific/<project-name> macro2.sublime-macro
Basically there will be created a file <project-name>.<key> for each key of project-specific dictionary, if value is a list. If value is a dictionary with subkey, then files <project-name> <subkey>.<key> will be created.
sublime-keymap configuration is an exception, because file-name must be Default. If you use here a subdictionary, your key can contain (case-insensitive) linux, osx, windows for os-specific keymaps, any other key will be mapped to Default (if there are multiple keys mapped to Default only the last processed is taken, values are not merged!).