Using code completion breaks navigation for arguments placeholders about vim-go HOT 6 CLOSED

I think I can fix this in the simple case where the completion text does not contain any placeholders, but it will remain for a case where a completion selection is made that contains placeholders, because Ultisnips does not support nested snippets.

from vim-go.

Ctrl-j works to navigate in the scenario you're describing, not ctrl-y.

from vim-go.

Ctrl-j works to navigate in the scenario you're describing, not ctrl-y.

ctrl-y is used to select an entry from a pop-up completion menu. ctrl-j / ctrl-k no longer work, placeholder is misplaced (see the last image).

from vim-go.

I misread your description. I thought you were trying to use ctrl-y to navigate after manually entering the first argument.

However, I'm unable to duplicate the problem you're describing.

I noticed that your gopls is not an official version. Can you update it with :GoUpdateBinaries gopls?

Also, what version of vim-go are you using? Your bug report says you're using the current version. Does that mean the latest master revision, the latest tagged release, or something else?

from vim-go.

I can duplicate what you're describing. I'm not sure what the solution is, though 🤔

from vim-go.

I think I can fix this in the simple case where the completion text does not contain any placeholders, but it will remain for a case where a completion selection is made that contains placeholders, because Ultisnips does not support nested snippets.

Again, thanks for the great job and that you are still keep rolling.

I'd find this solution satisfactory, because placeholders require and rely solely on UltiSnips engine and its features anyway.

Take care…

from vim-go.