-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged #3617 breaks UltiSnips placeholder mechanism #3625
Comments
I'm not able to replicate any changes in behavior between #3617 and master before it was merged. Perhaps your |
I'm seeing this as well, bisected to commit 3c223ad might it be an off-by-one in autoload/go/lsp/lsp.vim:12 ? I rolled back because my ultisnips contains a "macro" for printf
which is then used inside the snippet:
I could not complete at the placeholder anymore, all context seems to be lost.
|
Thank you, @timesselens. I can duplicate this now and see that it was working prior to #3617. |
Fix off by one in column calculation introduced in fatih#3617. Fixes fatih#3625
Fix off by one in column calculation introduced in fatih#3617. Fixes fatih#3625
It seems merged PR #3617 breaks code completion for function placeholders.
I had to roll back to preceding commit to make it work again.
After the PR, using code completion at function's argument placeholder (provided by UltiSnips), a selected identifier is inserted including its previously typed-in prefix.
For example, create a variable
sample := []int{1,2,3}
. Then later attempt to put it in a function argument using code completion, at a placeholder position invoke omni-completion menu, type leading three charssam
and selectsample
identifier - results in followingThe text was updated successfully, but these errors were encountered: