Can't get new o flag complete option working to add omnnicomplete results

[Pablo Giménez]

Hello.

Looking at the new features in Vim9.2, great release BTW, there is one that caught my attention, something I have been waiting for a long time.

The ability to get the results from several complete commands into one simple complete query.

Plugins like MuComplete where close, allowing to switch to different complete command, but the newly added o flag for the complete option looks like the proper solution.

Basically I want to press Ctrl-N and get results not only for keyword but also for omnicomplete, semantic aware results, I have been testing it with python where I use vim-jedi to

get omnicompletion working using the jedi#completions function.

Adding the o flag  doesn't seem to have any effect in the complete options offered when I press Ctrl-N, if I press Ctrl-X-O I got the expected results from omnicompletion, but those

results doesn't appear when I press Ctrrl-N.

These are the flags I use for complete:

set complete=.,w,b,k,o

Am I missing something? Are there some limitations with certain omnifuncs or jedi#completions needs tweaks to get it working?

I tried also using F and set complefunc to the same as omnifunc, but same result.

Using Vim 9.2.449

Thanks

--

Un saludo
Best Regards
Pablo Giménez

[Romain Lafourcade]

The feature works as expected in 9.2.321 in JavaScript files (using the stock javascriptcomplete#CompleteJS) and Python files (using the stock python3complete#Complete). Thank you for pointing it out to me by the way.

Note that the completion list is prioritized by "kind", so items from omnifunc may be way down the menu if "o" is at the end of "omnifunc".

You should try it in a buffer for which the "omnifunc" is not set by a plugin, or simply with "$ vim --clean", in order to rule out a Vim bug:

$ vim --clean +set\ complete=o filename.py

If "omnifunc" is set and you get language-aware completion, then it means that the feature works and that the problem is somewhere else. You should probably talk about this with the Jedi maintainers.

If not, then you may have found a regression introduced between 321 and 449, in which case you should head to Vim's issue tracker.