Closed sterlind closed 2 years ago
Looks great! Left a minor comment. Also, would it be possible to leave a few bullet points about how you got Windows working to save trouble for the poor next soul who tries 😅
I actually ended up using wsl2, even though I got windows working, just so I wouldn't have to have so many hacks making it hard for me to send PRs.
When working with WSL, the host vscode instance connects to a vscode server on the WSL vm. This happens automatically when you run "code" in WSL, as long as you have the "Remote - WSL" extension installed on the host. From there you need to:
pokey.command-server
extension on the host vscodevscode-parse-tree
, you need to clone that as well, build it, and link it into the vscode-server
extension folder: ln -s ~/.vscode-server/extensions/vscode-parse-tree ~/git/vscode-pars-tree
for instance.Remote-WSL
extension, you might need to manually delete the extension from the host side and try again.
Pretty straightforward; the Makefile tweak is because the package is named
tree-sitter-c-sharp
but the module produced is namedtree-sitter-c_sharp.wasm