I've been quite happy with nvim-cmp so far, but this looks excellent, I especially like the signature help sticking around while you're still filling out parameters! Looks like I'm tweaking my nvim config this evening!
I know, right? I had it working for everything except vue files. It was broken for days until i got the time to fix it. I'll try blink to see if it's worth.
"if you want you can do these other ones, but you're wrong.. that's okay" 🤣 but WOW the signature help is a game changer thanks so much Teej, I love this series!!
Even though I've been using nvim for a while now, and I have gone through configuring most of the things you talk about myself, this series is super fun, and I'm learning stuff I didn't know. props for the idea and the execution
You know i had seen this the other day when browsing the cmp docs is it better ? The way it was referenced made it sound like a much better completion engine
What would you recommend for writers in terms of getting definitions to show up like these autocompletes? Like you type “Westeros” and get a list of all places within it along with a one liner description.
This is great, is there any way to use it with the lspkind menu feature? You made a video a while back that set up lspkind to show where each completion item comes from, the function highlight is cool enough to switch over but the source label is very important to me
I also use blink.cmp, but encountered some weird behaviors. When I write the same vim.api.nvim_buf_set_lines( I get the same hover window as you get. But every time I type "0" for example it closes the hover and opens it up again when I type the ",". I do not get why and it looks much smoother on your video then for me. It is kinda distracting. Does someone maybe know why?
so is this complementary to nvim cmp or seperate project because i wanted to see the path of the import variable and i was able to do it in nvim cmp but in blink ill need to read more about how to do that. Also i have been tring disabling the auto suggestions while writing code and it really makes you remember the names of the commands which you will forget when using autocompelete. Also removed around 10-15 plugins from the neovim for the minimalistic. Creating my own remaps for the snippets.
I installed nvim via kickstart and added som custom plugins. But when I tried to disable nvim-cmp to try this plugin Ive got a lot of errors. I don't know why yet, but it may be a good idea to untangle the awesome kickstart project
To get to this point, we need: neovim < obviously lazy < package manager nvim-treesitter < configures builtin treesitter LSP's installed < external processes to neovim nvim-lspconfig < configures builtin LSP features blink.cmp < alternative to builtin omni completion ?
It’s very sad to switch to blink and just realize how slow the LSP server is. No blink can save that. But hey at least it’s fast when I am in lua files.
It shouldn’t require a setup call for basic functionality. It should only require it if defaults are not satisfactory. I’m so tired of dealing with setup calls for plugins that should just damn work.
@@런지부 So far i had 2 issues which were resolved the next day i woke up. If you don't use a lot of external cmp sources it should be very easy to replace and it offers most common native sources by default so do check that list. After those 2 issues I've had no problems since.
custom snippets next would be cool love the series!
YEEEEEEAH
YEEEEAH
I've been quite happy with nvim-cmp so far, but this looks excellent, I especially like the signature help sticking around while you're still filling out parameters! Looks like I'm tweaking my nvim config this evening!
This
yeah i didn't think i would need it but ... yeah seems like its a bit better than nvim-cmp
2:12 VERY IMPORTANT: Add blink.cmp as a dependency 'cause it can happen that it hasn't been loaded else.
(TJ did it, but didn't mention it)
Thanks!
Whoa!! Thanks!!
Really helpful. I use nvim-cmp so far but its configuration was the hardest that i experienced in nvim plugins :(
I know, right? I had it working for everything except vue files. It was broken for days until i got the time to fix it. I'll try blink to see if it's worth.
"if you want you can do these other ones, but you're wrong.. that's okay" 🤣 but WOW the signature help is a game changer thanks so much Teej, I love this series!!
Even though I've been using nvim for a while now, and I have gone through configuring most of the things you talk about myself, this series is super fun, and I'm learning stuff I didn't know.
props for the idea and the execution
I love how Teej is doing the videos faster than the previous one. I'm very hyped to be on 25th :D
The other day I said "I'll need to look into blink soon", started looking into it today and then this video goes live 😂 Thanks again my man!😊
This series would've helped me so much an year ago
Thank God I started my neovim journey after blink.cmp was already a thing. I bypassed all the pain people talk about when configuring nvim-cmp.
What is this sorcery. Teej on fire 🔥
Let's get right to it - love that
Ceo of neovim....
you too eh? [heheheh I see a horse with laser eyes]
he is one of core maintainer of neovim after all
this is fire
can you make a video on:
A new way to setup LSPs has been merged
You know i had seen this the other day when browsing the cmp docs is it better ? The way it was referenced made it sound like a much better completion engine
What would you recommend for writers in terms of getting definitions to show up like these autocompletes? Like you type “Westeros” and get a list of all places within it along with a one liner description.
You'd need a custom LSP.
Can you show how to use the built-in completion.
This is great, is there any way to use it with the lspkind menu feature? You made a video a while back that set up lspkind to show where each completion item comes from, the function highlight is cool enough to switch over but the source label is very important to me
I also use blink.cmp, but encountered some weird behaviors. When I write the same vim.api.nvim_buf_set_lines( I get the same hover window as you get. But every time I type "0" for example it closes the hover and opens it up again when I type the ",". I do not get why and it looks much smoother on your video then for me. It is kinda distracting. Does someone maybe know why?
Wanna give a try. Is it capable of showing the doc while scrolling through completions even before we actually select it huh?
basedpyright lsp does not offer such signature help, or is it because I didn't configure it properly?
so is this complementary to nvim cmp or seperate project because i wanted to see the path of the import variable and i was able to do it in nvim cmp but in blink ill need to read more about how to do that.
Also i have been tring disabling the auto suggestions while writing code and it really makes you remember the names of the commands which you will forget when using autocompelete. Also removed around 10-15 plugins from the neovim for the minimalistic. Creating my own remaps for the snippets.
cant get buffer words working with blink though
Thanks for this info (I dont even use neovim)
Hope you can implement this on the kickstart-nvim repo soon
I cant make cmdline completion work with blink for some reason.
mind blown
I installed nvim via kickstart and added som custom plugins. But when I tried to disable nvim-cmp to try this plugin Ive got a lot of errors. I don't know why yet, but it may be a good idea to untangle the awesome kickstart project
How does ur theme have that texture on it? Kinda feels like paper is it a plugin or terminal specific?
To get to this point, we need:
neovim < obviously
lazy < package manager
nvim-treesitter < configures builtin treesitter
LSP's installed < external processes to neovim
nvim-lspconfig < configures builtin LSP features
blink.cmp < alternative to builtin omni completion
?
This video is part of TJ's Advent of Neovim series, if you go back and watch the previous videos in the series, he covers all of those things 🙂
Nice vido, How to config source priority?
I'm confused, how it's easier than cmp? You setup, you pass capabilities to lsp. that's it.
Swapped to blink last week and ITS SO FAST
Blink and you'll miss it!
Is that it ??
D: y r u yelling at me
It’s very sad to switch to blink and just realize how slow the LSP server is. No blink can save that. But hey at least it’s fast when I am in lua files.
C-n and C-p, common emacs w :v
Is it JetBrainsMono?
looks like Berkeley Mono (paid font)
@@gerydony6531 ty
It shouldn’t require a setup call for basic functionality. It should only require it if defaults are not satisfactory.
I’m so tired of dealing with setup calls for plugins that should just damn work.
Is this better than nvim-cmp? How?
much much faster and fuzzy finding as well
The repo says it's still beta , is it unstable?
I should try it though
@@런지부 So far i had 2 issues which were resolved the next day i woke up.
If you don't use a lot of external cmp sources it should be very easy to replace and it offers most common native sources by default so do check that list.
After those 2 issues I've had no problems since.
Hmm, so that's it?
lets type something!
types kkk...
me af 🗿
first!
Ctrl-N and P are so wrong. Should be Ctrl-K and Ctrl-J instead
C-n and C-p are nice patterns to establish because they're ubiquitous, though.
benchod, this is way too easy to use as compared to nvim-cmp
Anyone use mini-completion? Why blink.nvim over mini-completion?
2 time but still curious, who no startup? (like alpha.nvim)
Thanks!
Wow!! Thanks!! I really appreciate it!