ProjectSpecific
Configure project specific commands, keymaps, etc. in your project-file.
Details
Installs
- Total 526
- Win 260
- Mac 162
- Linux 104
| Sep 5 | Sep 4 | Sep 3 | Sep 2 | Sep 1 | Aug 31 | Aug 30 | Aug 29 | Aug 28 | Aug 27 | Aug 26 | Aug 25 | Aug 24 | Aug 23 | Aug 22 | Aug 21 | Aug 20 | Aug 19 | Aug 18 | Aug 17 | Aug 16 | Aug 15 | Aug 14 | Aug 13 | Aug 12 | Aug 11 | Aug 10 | Aug 9 | Aug 8 | Aug 7 | Aug 6 | Aug 5 | Aug 4 | Aug 3 | Aug 2 | Aug 1 | Jul 31 | Jul 30 | Jul 29 | Jul 28 | Jul 27 | Jul 26 | Jul 25 | Jul 24 | Jul 23 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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!).