-
Notifications
You must be signed in to change notification settings - Fork 36
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
How can I make vim recognize when to <Enter> on autocomplete? #86
Comments
Hi @Odas0R, thanks for reporting. |
I face the same problem and it happens only when the multiline completion
is enabled. It was annoying enough for me to turn multiline completion off
(although not annoying enough to open a bug report.)
…On Sun, 1 Aug 2021, 08:30 Eransho, ***@***.***> wrote:
Hi @Odas0R <https://github.com/Odas0R>, thanks for reporting.
Just to make sure, did you enabled the 'Multiline Suggestions' feature in
Tabnine hub?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABTHN4WH7JXERM5UHDBDVTT2TSXZANCNFSM5BFBTD6Q>
.
|
Oh. Not using multiline won't affect suggestions quality? But yea, all good if I remove it of course! |
I guess I'll do the same 😅 |
Looks like a bug in our vim plugin, we will add it to our backlog. |
When I have the time, and if it wasn't solved yet I'll try to investigate, see if something comes up! |
I don't think this issue is related to TabNine itself but the plugin.
I'm getting cool suggestions and all, but it's super annoying that It doesn't automate
<Enter>
, instead it outputs NULL ASCII Code^@
Example:
Any help?
The text was updated successfully, but these errors were encountered: