nlua.nvim icon indicating copy to clipboard operation
nlua.nvim copied to clipboard

Error when trying to install the scripts/download_sumneko.lua

Open eddyekofo94 opened this issue 4 years ago • 4 comments

When I run :luafile scripts/download_sumneko.lua I get this error, is there something I am doing wrong because I don't fully comprehend the docs maybe (I am a noob into this) Here the error I get.

I got the latest Neovim installed etc.

  cwd = "/Users/eddyekofo/.cache/nvim/nlua/sumneko_lua/lua-language-server/",
  enable_handlers = true,
  enable_recording = true,
  interactive = true,
  pid = "ENOENT: no such file or directory",
  stderr = <userdata 2>,
  stdin = <userdata 3>,
  stdout = <userdata 4>,
  user_data = {},
  <metatable> = <1>{
    __index = <table 1>,
    _create_uv_options = <function 2>,
    _execute = <function 3>,
    _pipes_are_closed = <function 4>,
    _prepare_pipes = <function 5>,
    _reset = <function 6>,
    _shutdown = <function 7>,
    _stop = <function 8>,
    add_on_exit_callback = <function 9>,
    and_then = <function 10>,
    chain = <function 11>,
    chain_status = <function 12>,
    co_wait = <function 13>,
    is_job = <function 14>,
    join = <function 15>,
    new = <function 16>,
    pid = <function 17>,
    result = <function 18>,
    send = <function 19>,
    shutdown = <function 20>,
    start = <function 21>,
    stderr_result = <function 22>,
    sync = <function 23>,
    wait = <function 24>
  }
}
stack traceback:
        ...ins/neovim/nvim/plugged/plenary.nvim/lua/plenary/job.lua:370: in function '_execute'
        ...ins/neovim/nvim/plugged/plenary.nvim/lua/plenary/job.lua:413: in function 'start'
        ...ins/neovim/nvim/plugged/plenary.nvim/lua/plenary/job.lua:417: in function 'sync'
        plugged/nlua.nvim/scripts/download_sumneko.lua:25: in function 'run'
        plugged/nlua.nvim/scripts/download_sumneko.lua:55: in function 'build'
        plugged/nlua.nvim/scripts/download_sumneko.lua:62: in main chunk

eddyekofo94 avatar Jan 17 '21 01:01 eddyekofo94

had this issue too, the current fix is to manually clone the repo and call the script again.. seems like the clone part is failing

ellisonleao avatar Jan 19 '21 16:01 ellisonleao

I pretty much followed this guide since I am using MacOS, maybe the script is compatible only to Linux users.

eddyekofo94 avatar Jan 28 '21 23:01 eddyekofo94

Yeah, I don't have any way to check with mac atm.

I can try and fix it at some point, but honestly it's not too hard to run manually -- I just added a script for myself since it was just as easy as running the commands mostly.

tjdevries avatar Jan 30 '21 21:01 tjdevries

likely addressed by pull requests #16 & #17

klooj avatar Feb 08 '21 06:02 klooj