-
-
Notifications
You must be signed in to change notification settings - Fork 54
Feature request: linked/chained completion mode #299
Comments
Interesting.....!!! Hmm... mucomplete uses vim's native completion features. it does not fit the compe's approach... But I think it is very nice feature! I will consider it. And feel free to post your idea! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still relevant and pretty desired feature. |
This is the only thing I miss in nvim-compe. Please, consider to add it. :) Thanks |
The feature is discussed in #120. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@hrsh7th Do you think you could maybe move this issue to nvim-cmp? Would you consider it as part of amp-buffer source or even separate source? Would love to have that. :) |
You can request it in nvim-cmp issues. |
Absolutely, it's just that this issue already has some context added to it and moving it over would preserve it. |
I have read the feature. It is not for sources feature. |
And the issue title seems confusing. |
Apologies of it wasn't clearly reported. Not sure why it's called exactly. Do you think this is something that has to be provided by nvim-cmp's core or could be done as a source? |
It can be provided by nvim-cmp's core. |
mucomplete supports something they call 'extended completion', basically it helps quickly complete sequences of words by looking for word past one just matched.
It is separate mode which requires calling another completion method.
Please look at "Extending completion" example in https://github.com/lifepillar/vim-mucomplete to see exactly what I mean.
It was very nice to have when I was using mucomplete, I could see that being part of
buffer
source and definitely would use it daily. What do you think @hrsh7th?The text was updated successfully, but these errors were encountered: