-
Notifications
You must be signed in to change notification settings - Fork 35.2k
cmp
setup comes with a warning on the line that sets: cmp.mapping.complete()
#95
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
Comments
I get the same warning. |
After this I have no more warning: warning| This function requires 1 argument(s) but instead it is receiving 0.
PS: now I see that it is already written OS: Windows 10 Nvim release build Latest |
Fixed by #178 |
coffm049
pushed a commit
to coffm049/christian-kickstart.nvim
that referenced
this issue
Dec 12, 2023
Andrius595
pushed a commit
to Andrius595/kickstart.nvim
that referenced
this issue
Dec 28, 2024
As per LazyVim/LazyVim#4544 it creates confusion to the users who are just trying out the example to try things out. Better to avoid such misinterpretations in the future. I'm assuming this will also update the docs automatically as I can deduce from https://github.com/LazyVim/lazyvim.github.io/blob/25af26046a30be110f0aa19c87ad2a1a1e53ce45/lua/build.lua#L369-L372?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
cmp
setup comes with a warning on the line that sets:cmp.mapping.complete()
To Reproduce
Steps to reproduce the behavior:
]d
to go to the warning or open the quickfix window with<leader>q
Desktop (please complete the following information):
** Neovim Version **
Warning says
Help for the function shows an example to avoid completion in a specific circumstance, but doesn't explain the parameters. There's no help for
cmp.ConfigSchema
norcmp.ContextReason
.Putting an empty table fixes the warning, but I don't know if that breaks some functionality:
The text was updated successfully, but these errors were encountered: