ERROR: LoadError: LoadError: IOError: could not spawn `nvim --api-info`: no such file or directory (ENOENT)
Since, I presume, there is no nvim binary available to the CI. Perhaps there's a way to change that (i.e. make the nvim binary a dependency somehow?), but I'm not familiar with it, so this is another way to fix it. If we go this route, it seems like a better way of doing things would be to remove the code that runs nvim --api-info (and thus the try-catch this PR adds) and only read the api-metadata from the src/api-metadata file (or wherever we want to put it, that's just where I have it for now; created via a simple nvim --api-info > api-metadata).
To me, this might be the better way to go anyways, since that way if someone pulls a certain version of this library they know for certain what version of the nvim API it supports, etc.; thoughts?
@bfredl So, in order to get https://github.com/JuliaRegistries/General/pull/34118 (auto-)merged, the CI needs to be able to
import Neovim, but it's failing with:Since, I presume, there is no nvim binary available to the CI. Perhaps there's a way to change that (i.e. make the
nvimbinary a dependency somehow?), but I'm not familiar with it, so this is another way to fix it. If we go this route, it seems like a better way of doing things would be to remove the code that runsnvim --api-info(and thus the try-catch this PR adds) and only read the api-metadata from thesrc/api-metadatafile (or wherever we want to put it, that's just where I have it for now; created via a simplenvim --api-info > api-metadata).To me, this might be the better way to go anyways, since that way if someone pulls a certain version of this library they know for certain what version of the nvim API it supports, etc.; thoughts?