Closed ackalker closed 10 years ago
Workaround: always accept a completion, even if it's just temporary:
To make sure that omni completion doesn't get 'stuck' on a particular identifier, always accept something from the omnicomplete window. If it's a function, add an empty pair of parentheses (important!), then add a semicolon (perhaps not required, but it works) and press Enter.
This appears to 'reset' the omni completion so that next time it will complete on the right identifier. The temporary completion can now be deleted.
Wow, that was fast! Thanks :-)
Problem: Omnicomplete after
<identifier>.
sometimes shows stale completions (from a previous omnicomplete). Seen with:tern_for_vim@master
Steps to reproduce:
.tern-project:
example.js:
Now, edit the
example.js
file with Vim:cheerio.
and start omni complete (C-X C-O) after the.
. Observe the results are correct.cheerio.
then typeconsole.
then start omnicomplete again. Observe the completion results are forcheerio.
, not forconsole.
.