search

LuaLS / vscode-lua

Release lua-language-server for VSCode
https://github.com/LuaLS/lua-language-server
MIT License
182 stars 52 forks source link

Failing to open Addon Manager #117

Closed Bilal2453 closed 1 year ago

Bilal2453 commented 1 year ago

Which OS are you using?

Windows

Expected Behaviour

When creating and opening a workspace, pressing Ctrl + Shift + P, and "Open Addon Manager", the Addon Manager is opened without any errors.

Actual Behaviour

An error prompt appears: image

Reproduction steps

  1. Make and open a workspace.
  2. Press Ctrl + Shift + P, "Lua Addon Manager", press Enter.
  3. The error should show up.

Additional Notes

This was tested on the extension version 3.6.18, on Windows. Note that it only happens on Windows. This was not discovered by me, rather it was reported by someone else who was following my instructions. I cannot replicate it myself on Linux.

Log

No output at all in the Lua Addon Manager dropdown.

carsakiller commented 1 year ago

Nothing changed that should be causing this. If the command is not found, that means the addon manager is never being initialized. Please make sure the addonManager.enable setting is not set to false.

Bilal2453 commented 1 year ago

@carsakiller I too thought it was disabled in the settings, but it doesn't seem like it: image

carsakiller commented 1 year ago

The rest of the extension works as expected (completion, type checking, etc.)?

Bilal2453 commented 1 year ago

Yes sir.

Bilal2453 commented 1 year ago

It may be worth noting that they had about 6-7 Lua extensions enabled, made them disable most of them. The only ones left enabled where this one, and the Lua Debugger one by actboy168, and another for it seems Luau.

carsakiller commented 1 year ago

I will have to look into this at a later time

Bilal2453 commented 1 year ago

Sorry, I can't seem to be able to provide any further debugging info regarding this. If you look into this and don't find anything, it may not be worth keeping the issue opened.

carsakiller commented 1 year ago

I am not able to reproduce in v3.6.18. Without the output from the VS Code developer console, I cannot find a cause for this problem. If the person following your instructions can provide that, we can reopen this issue, but I'm going to close it for now.