Error executing vim.schedule callback about nvim-compe HOT 16 CLOSED

Yep, it's fixed. Thank YOU for fixing this :)

from nvim-compe.

update: this is easily reproducible in c when you type #include <std.|>. | is the cursor and that's where the error happens.

Character.match = function(byte1, byte2)
-  local diff = byte1 - byte2
+  local diff = (byte1 or 0) - byte2
  return diff == 0 or diff == 32 or diff == -32
end

Doing this solves the issue but I don't know if this is a good permanent solution

from nvim-compe.

Sorry for the lately reply.

I can't reproduce clangd/typescript-language-server both.

It is bit difficult (may be it is a potential bug of the matcher.lua because it is a complex codes)

from nvim-compe.

no worries. I can wait however long it would take until there's a solution for this :)
I've found my workaround so this isn't that big of an issue.

from nvim-compe.

Sorry for annoying.

If you can reproduce easily, please detect the error place by debug branch.

from nvim-compe.

#71

from nvim-compe.

Ok, I've tried that and here's the debug info. https://paste.sh/zcGWAXps#HKoNPs_FWtgJpF2pGnvEG__E

from nvim-compe.

Thank you! I will debug it.

from nvim-compe.

Hm... I want to detect the input and the word that cause this error.

Matcher.score(
  Matcher.bytes2string({ 105, 110, 99, 108, 117, 100, 101 }),
  Matcher.bytes2string({ 105, 110, 99, 108, 117, 100, 101 })
)

It works fine (no errors).

Could you try to detect the word/input?

from nvim-compe.

The word is #include <. The error happens as soon as I press <
The full file is this.

#include <

int main(void)
{
  printf("Hello world");
}

from nvim-compe.

OK. I will push debug code for the above concern.

from nvim-compe.

Realy thank you for your help.

I've pushed to debug code.
If you have a time, please provide last debug information.

from nvim-compe.

Here's the latest one. https://paste.sh/IBEEkb1Q#gPFs1ST_c7BuAm3gFUUJ9RHh

from nvim-compe.

Thank you very much!

I get the cause may be. will fix it soon

from nvim-compe.

Wa--- issue automatically closed.

from nvim-compe.

I think the issue was solved on the latest master.

from nvim-compe.