C0D312 wrote:Did you get it working? Let me know if you need help.
Okay. I stepped out for lunch, and now I need to refactor a bit.
But I'll ping back definitely in a bit. Thanks.
C0D312 wrote:Did you get it working? Let me know if you need help.
C0D312 wrote:It's funny because I came across that same exact problem. I tried a few things such as closing the autocomplete at the beginning of the plugin and setting a short timeout. However, nothing worked as smooth as just setting auto_complete_triggers to '.' for java (in Display-Java's case). I'll play around with in though and see what I can do.
self.view.run_command('hide_auto_complete')
def activate_ac(self):
self.view.run_command('auto_complete', {
'disable_auto_insert': True,
'api_completions_only': True,
'next_competion_if_showing': False
})
view.run_command('hide_auto_complete')
sublime.set_timeout(self.activate_ac,100)
C0D312 wrote:Awesome. I got it working. All you need to do is set a timeout to run_command('auto_complete')
This is the code I used:def activate_ac(self):
self.view.run_command('auto_complete', {
'disable_auto_insert': True,
'api_completions_only': True,
'next_competion_if_showing': False
})view.run_command('hide_auto_complete')sublime.set_timeout(self.activate_ac,100)
I tried a few things such as closing the autocomplete at the beginning of the plugin and setting a short timeout.
Users browsing this forum: Narretz and 4 guests