When completing the popupmenu always shows the best result in the top row. But when the pmenu opens above the completion, the top row can be located anywhere above the completion.
Describe the solution you'd like
There should be an option, that the best match is always closest to the point of completion. Either the last or first row, depending if the popupmenu opens above or under the point of entry.
Also then a new keymap would be needed, because with this options set, the next 'worser' popupmenu match is not always in the 'down' direction.
Describe alternatives you've considered
Tried to find some vim configuration to enable this behavior.
Context
Here the best match is always in the same place:

But when pmenu open above, the best match can be in different locations:
—
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
@BonaBeavis what framework or plugin you are using for this? (That popup menu)
—
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
@TarunavBA hrsh7th/nvim-cmp: A completion plugin for neovim coded in Lua.
—
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
Hey @BonaBeavis I think you should frame this issue in here because this is a completion problem for Neo vim. I think you can close this issue now.
—
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
nvim-cmp doesn't even use builtin popupmenu. It draws its own popupmenu using floating window. However, this feature request may still be applicable to Vim.
—
Reply to this email directly, view it on GitHub.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.![]()
closing for reasons mentioned in the PR: #16321 (comment)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Closed #9399 as not planned.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()