Skip to content
This repository has been archived by the owner on Feb 3, 2024. It is now read-only.

Use completion settings, not Preferences #68

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mitchr
Copy link

@mitchr mitchr commented Sep 8, 2015

Preferences.sublime-settings was previously used for completion
variables. It makes more sense to use completion.sublime-settings.

Preferences.sublime-settings was previously used for completion
variables. It makes more sense to use completion.sublime-settings.
@quarnster
Copy link
Owner

Well, no, because then you won't have .sublime-project settings respected (which are queried via view.settings()). You are correct however that it should fallback to completion settings if no view settings are set. I think a helper function is in order which pretty much does (untested) def get_setting(view, settings, key, default=[]): return view.settings().get(key, settings.get(key,default)).

@bangive
Copy link

bangive commented Nov 13, 2015

Sorry for asking here, but i don't see issue category.
I already installed this plugin but i don't know how to use it. I don't see any instruction.
Is this plugin support autocomplete for class, method from a package jar or gradle dependency.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants