hrsh7th

### Remove `experimental.native_menu` and add `view.entries = 'native'` instead. ``` cmp.setup { ... experimental = { native_menu = true } ... } ``` ↓↓↓ ``` cmp.setup { ... view =...

### Remove `documentation` and add `window.documentation` instead. ``` cmp.setup { ... documentation = false, ... } ``` ↓↓↓ ``` cmp.setup { ... window = { documentation = false, } ......

### Remove all default key mappings (workaround is existing) All key mappings have been removed by https://github.com/hrsh7th/nvim-cmp/commit/93cf84f7deb2bdb640ffbb1d2f8d6d412a7aa558. If you want to achieve the previous behavior, you can use the built-in...

### nvim-cmp will only work on nvim v0.7.x or higher. status: applied The nvim v0.7.0 contains the `Lua version APIs`. So nvim-cmp will use it and drop supporting the previous...

I think the nvim-cmp should not have any view related features except the default float-win menu. But for now, I can accept PR.

> Would it make sense to calculate the row to display the wildmenu on based on cmdheight instead of a hard coded value? It's make sense. To be honest, I...

That's because I think it's basically an anti-pattern to absorb the differences in people's preferences in one implementation in one repository. We could have just a single implementation if you're...

I don't think nvim-cmp does not have any built-in sources is make good ecosystem and it does not make unnecessary effort to the user. For example, you did make `cmo-fuzzy-buffer`....

I think distributed design is cut off the maintein cost. For example, I don't maintein cmp-ultisnips and cmp-luasnip. It's supporting by other mainteners. I can focus core functionality and stability.

As the developer of telescope.nvim mentioned, I think it's a bad idea to implement features in this repository that I'm not using. They are not maintained and bug reports are...