hrsh7th
hrsh7th
I thought this feature was feasible with the current feature set, but the perfect solution seems difficult. Therefore, it is necessary to add a function. Note that this feature is...
What I want to say is that nvim-cmp implements the text state after "expand" as the server intended, but the text state at the time of selection is not always...
Yes. `` combo can be usable as workaround. But you have to write some codes.
It's may work for you. ```lua [''] = function() local active = cmp.get_active_entry() if active then return cmp.close() end local next = 'lua require("cmp").select_next_item()' local prev = 'lua require("cmp").select_prev_item()' local...
Reluctantly, I needed vim.schedule to make it work. The nvim-cmp mapping process needs to be refactored. Anyway, I think the following implementation works. ``` [''] = function() local active =...
Please explain how annoying with current setting.
Isn't the `keyword length` option enough? Sorry. I am careful about exposing the options as public. I can add this but I want to know the rational reason.
I'd tried `THROTTLE_TIME=1500` and `SOURCE_TIMEOUT=100`. It will cause the strange behavior...
I hope to know,the ideal behaivior.
Therefore, the "debounce" function is required. Hmm ... for now, I'll provide a workaround for debounce. It seems that we have to think continuously.