search

WilliamVenner / vscode-glua-enhanced

👨‍💻 Garry's Mod Lua VSCode Extension for enhanced auto completion, wiki integration, snippets, color palette, and much more...
https://marketplace.visualstudio.com/items?itemName=venner.vscode-glua-enhanced
GNU General Public License v3.0
410 stars 10 forks source link

Code analysis (find globals) fails to work under WSL #20

Closed chelog closed 3 years ago

chelog commented 3 years ago

Hey there. I'm pretty new to WSL stuff however I developed under both Unix and Windows systems. I set up fresh WSL build and set up server, everything works fine (including all other extensions) except the globals scan. VSCode ceases to autocomplete global tables under WSL, but working under plain Windows just fine. If you need any additional reports, I would gladly send them if you tell me where to look

My setup: WSL2 running Ubuntu 20.04, host is Windows 10 build 19042, VSCode:

WilliamVenner commented 3 years ago

Huh? Does WSL have anything to do with this? Is VSCode running on Windows, but the files you're editing on the WSL filesystem?

chelog commented 3 years ago

@WilliamVenner yes, my gmod server is fully installed into Linux under WSL2. VSCode client is running in host Windows connected to VSCode server in WSL. You need to install some extensions into VSCode server under WSL, like this (uninstalled it just to show the button):

My whole setup is looking something like this, project is set up in server root:

I think it has something to do with gluadump not being able to properly list and read files that are located in WSL filesystem. If you never tried WSL in VSCode, I recommend trying it yourself to better understand (its kinda cool anyway!), it's fairly easy and can be done under 10 minutes if your network is good: https://docs.microsoft.com/en-us/windows/wsl/install-win10#manual-installation-steps https://code.visualstudio.com/docs/remote/wsl

chelog commented 3 years ago

Just found the article in VS docs that may help to solve this: https://code.visualstudio.com/api/advanced-topics/remote-extensions

And using info from there I found out that in F1 -> Show running extensions glua enhanced is listed in regular Windows, but not in WSL, meaning the extension wouldn't even try to start under WSL

WilliamVenner commented 3 years ago

I believe this should be fixed in 2.3.2.

chelog commented 3 years ago

@WilliamVenner I can confirm that extension is now up and running in WSL fixing the "does not exist" error. However, dump isn't working still I guess:

Running heatmap tells there's access error:

Adding permissions gives following error: EDIT: Removing gluac.lua and re-running command fixed heatmap error, it was broken cache I guess

But globals are still not working, temp folder is empty: