![Gitter](https://badges.gitter.im/Join Chat.svg)
SublimeJEDI is a Sublime Text 2 and Sublime Text 3 plugin to the awesome autocomplete library Jedi
cd ~/.config/sublime-text-2/Packages/
git clone https://github.com/srusskih/SublimeJEDI.git "Jedi - Python autocompletion"
- Open command pallet (default:
ctrl+shift+p
) - Type
package control install
and select commandPackage Control: Install Package
- Type
Jedi
and selectJedi - Python autocompletion
Additional info about to use Sublime Package Control you can find here: http://wbond.net/sublime_packages/package_control/usage.
By default SublimeJEDI will use default Python interpreter from the PATH
.
Also you can set different interpreter for each Sublime Project.
To set project related Python interpreter you have to edit yours project config file.
By default project config name is <project name>.sublime-project
You can set Python interpreter, and additional python package directories, using for example the following:
# <project name>.sublime-project
{
// ...
"settings": {
// ...
"python_interpreter": "$project_path/../../virtual/bin/python",
"python_package_paths": [
"$home/.buildout/eggs",
"$project_path/addons"
]
}
}
NOTE: Please note that Python will goes through the directories from "python_package_paths"
to search for modules and files. In other words, each item in "python_package_paths"
list is a directory with extra packages and modules, not a direct path to package or module.
When setting paths, Sublime Text Build System Variables and OS environment variables are automatically expanded. Note that using placeholders and substitutions, like in regular Sublime Text Build System paths is not supported.
If you want auto-completion on dot, you can define a trigger in the Sublime User or Python preferences:
# User/Preferences.sublime-settings or User/Python.sublime-settings
{
// ...
"auto_complete_triggers": [{"selector": "source.python", "characters": "."}],
}
If you want auto-completion ONLY on dot and not while typing, you can set (additionally to the trigger above):
# User/Preferences.sublime-settings or User/Python.sublime-settings
{
// ...
"auto_complete_selector": "-",
}
Find function / variable / class definition
Shortcuts: CTRL+SHIFT+G
Mouse binding, was disabled, becase it's hard to keep ST default behavior.
Now you can bind CTRL + LeftMouseButton
by themself in this way:
# User/Default.sublime-mousemap
[{
"modifiers": ["ctrl"], "button": "button1",
"command": "sublime_jedi_goto",
"press_command": "drag_select"
}]
Find function / method / variable / class usage, definition.
Shortcut: ALT+SHIFT+F
.
Show docstring as tooltip.
For ST2: Show docstring in output panel.
Shortcut: CTRL+ALT+D
.
If available mdpopups is used to display the docstring tooltips. To modify the style please follow mdpopups' styling guide.
Basically a Packages/User/mdpopups.css
is required to define your own style.
To specify rules which apply to Jedi tooltips only, use .jedi
selector as displayed in the following example.
/* JEDI's python function signature */
.jedi .highlight {
font-size: 1.1rem;
}
/* JEDI's docstring titles
h6 is used to highlight special keywords in the docstring such as
Args:
Return:
*/
.jedi h6 {
font-weight: bold;
}
mdpopups provides a default.css which might be used as cheat sheet to learn about the available styles.
Show calltip in status bar.
Exposed command is sublime_jedi_signature
.
SublimeJEDI allow fill up function parameters by default. Thanks to @krya, now you can turn it off. Function parameters completion has 3 different behaviors:
-
insert all function arguments on autocomplete
# complete result func(a, b, c, d=True, e=1, f=None) # sublime_jedi.sublime-settings { "auto_complete_function_params": "all" }
-
insert only required arguments that don't have default value (default behavior)
# complete result func(a, b, c) # sublime_jedi.sublime-settings { "auto_complete_function_params": "required" }
-
do not insert any arguments
# complete result func() # sublime_jedi.sublime-settings { "auto_complete_function_params": "" }
Sublime Text has a bit strange completion behavior and some times does not adds it's own completion suggestions. Enabling this option to try to bring more comfortable workflow.
-
Suggest only Jedi completion
# sublime_jedi.sublime-settings { "sublime_completions_visibility": "jedi" }
or
# sublime_jedi.sublime-settings { "sublime_completions_visibility": "default" }
-
Suggest Jedi completion and Sublime completion in the end of the list
# sublime_jedi.sublime-settings { "sublime_completions_visibility": "list" }
Please note, if you are using SublimeAllAutocomplete - you should not care about this option.
To change logging level of the plugin - change logging_level
value in settings.
Possible values: "debug", "info", "error"
# User/sublime_jedi.sublime-settings
{
// ...
"logging_level": "error"
}
It's a common issue for ST3.
All language related settings are stored in Python Package.
There is a Completion Rules.tmPreferences
file where defined that completion should be cancelled after a keyword (def, class, import & etc.).
To solve this issue Sublime Jedi plugin already has a proper Completion Rules.tmPreferences
file for ST2, but ST3 ignores it.
Some workarounds how to update completion rules and fix the issue:
1. Delete your Sublime Text Cache file `Cache/Python/Completion Rules.tmPreferences.cache`
2. Download [Completion Rules.tmPreferences.cache](https://raw.githubusercontent.com/srusskih/SublimeJEDI/master/Completion%20Rules.tmPreferences) to `User/Packages/Python/`
1. install Package https://packagecontrol.io/packages/PackageResourceViewer
2. cmd+shift+p (Command Panel)
2.1. type `PackageResourceViewer: Open Resource`
2.2. type `python` and select Python package
2.3. type `Completion Rules.tmPreferences`
2.4. remove `import` from the regexp.
2.5. save