Open keith-hall opened 8 years ago
Likely the same underlying issue as https://github.com/sublimehq/sublime_text/issues/1834. Actually not, because the issue was closed mistakenly.
@deathaxe, on which platforms did you see this was fixed on?
I tried on Linux, and still nothing is logged in the console with sublime.log_commands(True)
and clicking on an autocomplete entry. And EventListener
on_post_text_command
/on_post_window_command
methods aren't fired either.
(my particular use case is actually solved by being able to call an arbitrary command for my plugin's completions, but I wanted to check in case other people want this functionality but can't control the completions...)
I didn't realize it's about not publishing the commit_completion
to plugins, but thought it is about clicking on auto completion items doesn't do anything at all.
In light of the comment at https://github.com/sublimehq/sublime_text/issues/4023#issuecomment-802809082, I'm going to change this issue from a bug to a feature request for clicking on an autocompletion entry to fire an event listener.
Expected behavior
That clicking on an autocompletion entry would have the same behavior as pressing Tab to commit the entry, on all platforms, so that plugins can consistently respond to both events.
Actual behavior
Clicking on an autocompletion entry doesn't fire any command, although the text is correctly inserted into the document.
Steps to reproduce
sublime.log_commands(True)
auto_complete
commit_completion
with"auto_complete_commit_on_tab": true
andinsert_best_completion
with"auto_complete_commit_on_tab": false
sublime.log_commands(True)
auto_complete
Tried on
3103
and3109