hrsh7th

The workaround. ``` lua

https://github.com/hrsh7th/nvim-cmp/issues/435 https://github.com/hrsh7th/nvim-cmp/issues/266

Now, We have `performance` configuration section. So I can add this feature. Rough sketch. ```lua cmp.setup { performance = { trigger_debounce_time = 500 } } ```

I'll organize the configuration schema.

Hm... it's bit difficult but I have same opinion. we should add the `cmp.complete({ ... }, callback)`

Wait. We should consider it more depply.

I don't want to add `fallback` but I can consider adding the `callback`. ```lua cmp.complete({ ... }, function() if not cmp.visible() then cmp.complete() end end) ```

I'm continuously considering this. In my current thoughts, we should add `cmp.complete_sync`

First, since nvim-cmp retrieves data from multiple sources, we need to hit the callback when all sources have been retrieved. Also, should the callback be called if the user inputs...

Why was the buffer source specified twice? (Is it just example?)