perf: use builtin for key normalization

[tomtomjhj]

After #986, @zeertzjq added the keytrans() function for translating byte rep of keys to key notation form in neovim/neovim@907fc8a. This can be used for normalization.

This reduces running time of prepare() from about 16ms to 6ms on my setup.

btw I' curious about why keymap.t manually replaces < instead of using nvim_replace_termcodes (f2f6dce). nvim_replace_termcodes is slightly faster.

[hrsh7th]

thank you.

[RayGuo-ergou]

Hi @tomtomjhj @hrsh7th This seems breaks keybind for <c-j>. I don't have too much knowledge about key binds but <c-j> seems a special key that always has issue? ( I have seen in different places like nvim and zellij )

To reproduce what I am facing, with the config below

vim.api.nvim_set_keymap('i', '<c-j>', '<cmd>echo "Hello"<cr>', {})

local cmp_select_next_item = function(fallback)
  if cmp.visible() then
    cmp.select_next_item({ behavior = cmp.SelectBehavior.Select })
  else
    fallback()
  end
end

cmp.setup({
  mapping = cmp.mapping.preset.insert({
    ['<C-j>'] = cmp.mapping(cmp_select_next_item),
...

Even the cmp menu is opened, it still prints Hello, However, I bind <c-k> the same way but it does not have this issue.

I have removed my keybind to <c-j>, so this is more like a report/FYI this might cause some compatibility issue.

Thank you for your work on this plugin btw!

[tomtomjhj]

Thta seems to be nvim bug. reported neovim/neovim#30887

[dav-cho]

After this commit, I'm seeing a slight delay when typing < in insert mode. #2069 does not fix this. Any ideas on how to address?