Error executing vim scheadule

[vuki656]

Hey, since I think 2-3 days ago I'm getting a constant error when in insert mode and tying.

Since no one else reported it yet I'm assuming it's something having to do with my local setup, but I haven't really changed any configuration for null-ls.

Any help would be appreciated.

[jose-elias-alvarez]

Looks like error output from a specific source, and since you see it when typing, it's most likely a diagnostics source. Could you try to figure out which one? I don't know if we've made any changes that would affect it, but it's definitely a possibility.

[jose-elias-alvarez]

Hmm, I don't normally use selene, but a fresh install from cargo seems to work normally for me. Does it work when you run it from the command line?

[vuki656]

I just did cargo install Selene --force to reinstall it and the error persists.

Same error running from the console so I guess it's something unrelated to null-ls.

Thanks for the help anyways.

[Cenobantur]

Sorry if you already resolved it but to fix it you have to specify the path to the file containing the rules.
In selene.toml, instead of std="vim" you have to set std="/path/to/vim.toml"

[vuki656]

Oh, interesting.

Where would one find vim.toml and what is its purpose?

[Cenobantur]

Oh sorry, I just applied my use-case to your problem, vim.toml is the file where you set the rules you want selene to lint, in my case I use it for Vim.
The file can have any name, I think the default is std="lua51".
I had that same error until I set that file.
Selene can't find the standard library you are using or you didn't specify it in selene.toml.