Beau

I totally understand, there were quite a few different ones flying around. This solution should be quite a bit more robust in its approach compared to what was floating around,...

No problem :)

Great I have this branch set up now, how shall I call this in a function? if I try :call COQmarks_available() I get an error where it seems its feeding...

I have it working great with this snippet ```lua local t = function(str) return vim.api.nvim_replace_termcodes(str, true, true, true) end _G.tab_complete = function() if vim.fn.pumvisible() == 1 then return t ""...

> the naive approach has an issue though, the user wants use the `` key right, and I presume they want `` to work normally when they don't want to...

I'm going to use this PR for now because I am happy with it as it is despite not being perfect

I am seeing this issue here. We need a space after the icons for when no subtext to it's not juxtaposed next to the ] 

> @beauwilliams please set `coq_settings.display.pum.kind_context` to `[" [", " ]"]`, or whatever you want it to be. > > I think like for different fonts, the spacing is different? so...

Good news is the new option works. But it seems I still have the same issue for the BUF type 

If we don't ever have anything but text for the buffer completion type. We could just have it say [aA Text] like the lsp completion at the top there, or...