Auto pop up behaviour makes `completeopt=longest` unusable

[mangelozzi]

Describe the issue When typing say file paths, its very conviant to have completeopt=longest,menuone. This means that when typing, and then pressing auto-complete, it will add the longest common match, and insert it. When traversing dirs, you don't want to be fiddlind around selecting each dir as you get matches, it would be faster just to type the filepath.

However with completion-nvim, when the pop up menu automatically pop ups, the longest option make nvim insert text immediately. E.g. If you are typing HTML, soon as you type < it inserts <figcaption>, its unsuable, trying to delete it and fix it is futile.

I do like the auto popup behaviour (g:completion_enable_auto_popup=1), because I don't know how much of a long variable name to type before pressing auto complete.

Describe the solution you'd like If you the user does not initiate the popup menu via a hotkey, i.e. the menu pops up on its own from a trigger word, or g:completion_trigger_keyword_length etc, the menu should not auto insert the match automatically (ignore longest, behave like noselect.

I can't think of a logical use case where it would be beneficial to have autocomplete setup to automatically insert the first match soon as the user types. i.e. g:completion_enable_auto_popup = 1 and completeopt=longest,....

Describe alternatives you've considered Read all the options of completeopt and wildmenu and completion NVIM trying to figure out a way to keep longest beheviour, but have noselect with NVIM lsp. completeopt is a global option (also affects cmd line), i.e. it's not buffer local.