Gno repo management in gnopls #9
Description
Hey there!
I’m working on an IntelliSense plugin for VSCode and planning to hook it up with your gnopls server. I wanted to run an idea by you and get your thoughts.
Right now, the GNOROOT variable points to wherever the gno repo is cloned on the user’s machine. But I’m thinking about changing things up so the gno repo is included right in the root of the gnopls project. That way, the repo could be updated directly through my extension’s settings in VSCode, and users wouldn’t need to mess around with manually updating or even having the gno repo on their system at all.
As it stands, people have to clone the repo to install gno and its dev tools. But in the future, it might be as simple as grabbing an executable or using something like Homebrew. Including the repo with gnopls would save users from having to worry about cloning or setting up paths, making everything smoother for them.
What do you think this approach? Can it cause any issues ?
Thanks in advance for your feedback ! 🙏