Errors when I save any file

[ahmedelgabri]

I'm trying null-ls to see if I can replace efm or not. But when I save any file I get the following error.

E5108: Error executing lua [string "luaeval()"]:1: attempt to index global '_' (a number value)
stack traceback:
        [string "luaeval()"]:1: in main chunk
Press ENTER or type command to continue

Here is the commit of what I'm trying to do ahmedelgabri/dotfiles@1704e1c

Nothing fancy at all, I only have

local nls = require 'null-ls'

nls.config {
  debounce = 150,
  sources = {
    nls.builtins.formatting.stylua,
  },
}

[jose-elias-alvarez]

We don't use luaeval anywhere in the code base, so I don't think this is an issue on our end. Your config is pretty large, so I'd try to start with the minimal config from the README and go from there. Feel free to open an issue if you're able to put together a minimal reproduction, because I've never seen this one before.

[ahmedelgabri]

Something else, maybe will help. Notice that the fzf file is under after/plugin & not loaded through lua explicitly anywhere. So this might be also the issue… I will try to the minimal config & see.

[jose-elias-alvarez]

Okay! I think I have an idea. I put together a minimal config with null-ls, plenary, and your config, and I notice that _G._ is nil after setting up null-ls, but as soon as I call vim.lsp.buf.formatting() on a Lua file, it becomes a number. I loaded up a few files from Plenary's async library and noticed that there's a lot of random global variables, so I think what's happening is that your global variable is getting redefined by Plenary.

If this is the case, changing the name of the variable should fix it. Could you give it a shot? If that fixes it I'll try to put together a Plenary PR to avoid using global variables where possible.

[ahmedelgabri]

Looks like this was the case indeed, I changed the global variable name & everything seems to be working fine now. I will monitor if this happens again. Thanks for the help!

[jose-elias-alvarez]

I was a little too quick to blame Plenary. In fact, the issue came from the diff implementation I borrowed from Neovim 0.5.1. 2b88fac should take care of it!

[ahmedelgabri]

Great! now I can keep my beloved _ variable :D thanks again!