Nice to see the 1.0 release. Congrats to the team. 
Since we have now stabilized on a mojo syntax, it would be nice to see the LSP expand from just the current VScode + forks to the general ecosystem, in my case Zed. For this particular case, there’s been an unofficial way to get the LSP working.
But in general, does the team have plans( or need of contributions) for the LSP in other ecosystems?
The whole point of the language server protocol is that it ends the problem of ages past where a language needed extensive individual support in every IDE. If you look into the community plugins, you’ll see that they’re mostly some boilerplate to wire up the plugin and then a “find the LSP binary” plugin.
Our tools team is already stretched thin as-is, with a lot of the work going into the LSP binary itself. As a result, it’s difficult for us to officially commit to support for other IDEs. We do, of course, welcome community and encourage involvement here. People actively using IDEs are more likely to catch updates, plugin API changes, etc that would break the plugin than we are, especially for less-popular IDEs like Zed or Helix.
As you mentioned, there are already a few Zed mojo LSP impls, so it might be worthwhile to ping the people maintaining them and see if you all can set up a github org either for Zed specifically or maybe for community Mojo LSP extensions in general.
+1 to what Owen said. Mojo extensions for specific editors should be community driven. If this requires adding new capabilities in the Mojo LSP itself, please post here, Mojo team will be happy to help (and soon, accept contributions).
There seems to have been some discussions about Mojo support in zed (zed-industries/zed · Discussions · GitHub).
Thank you, I’ll look into it. Good luck today on Modcon.
This PR might be interesting, in case you have not seen it 