Open guillermooo opened 10 years ago
While skipping through the changelog:
view.match_selector(point, selector)
is not documented, can probably be written as view.score_selector(point, selector) != 0
and sublime.score_selector(view.scope_name(point), selector) != 0
though.view.extract_completions(prefix)
window.get_output_panel(...).window()
indicates if the panel is visible or notNot sure where to put this though.
ref: http://www.sublimetext.com/forum/viewtopic.php?f=6&t=10663&p=54272#p54136
from: https://github.com/FichteFoll/UnofficialDocs/issues/15
Since I will likely forget about what features are currently not documented in the official API Docs and do not have the time to add them all I'm creating an issue here to keep track of all the missing things.
EventListener.on_query_completions(self, view, prefix, locations)
which allows two different return types andsublime.INHIBIT_WORD_COMPLETIONS
, used as a second return value when a tuple*Command.*_
methods with the event parameter and unwrappedargs
(e.g. "run_", "isenable")?*Command.is_checked
for use as a menu item commandsublime_plugin.run_timed_function(f, name, event_name, timeout)
usually not necessary to call since it's already used on direct plugin calls but maybe interesting for multi-threaded stuff?sublime_plugin.reload_plugin(fname)
should not be used regularly but still interesting?Quick edit:
[x] Completions (
.sublime-completions
file as well as generated by event listeners) support displaying a description which can be added by separating it with\t
in the "trigger" key. Example: