ProjectSpecific
Configure project specific commands, keymaps, etc. in your project-file.
Details
Installs
- Total 526
- Win 260
- Mac 162
- Linux 104
| 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 | 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 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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!).