New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add tern_inhibit_word_completions config option #163

Merged
merged 1 commit into from May 28, 2017

Conversation

Projects
None yet
2 participants
@nickw444
Contributor

nickw444 commented May 27, 2017

It doesn't make sense to have buffer completions when tern is configured correctly and providing accurate file and project-level completions.

This PR makes the plugin configurable to allow buffer-based completions to be disabled.

Docs for functionality:

([[trigger, contents], ...], flags)
Basically the same as above but wrapped in a 2-sized tuple. The second element, the flags, may be a bitwise OR combination of these flags:

sublime.INHIBIT_WORD_COMPLETIONS
Prevents Sublime Text from adding its word completions to the completion list after all plugins have been processed. This consists of any word in the current document that is longer than 3 characters.

http://docs.sublimetext.info/en/latest/reference/api.html#sublime_plugin.EventListener.on_query_completions

@marijnh marijnh merged commit 2e5fd68 into ternjs:master May 28, 2017

@marijnh

This comment has been minimized.

Member

marijnh commented May 28, 2017

Makes sense. Merged!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment