-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linden Scripting Language doesn't seem to be working. #1
Comments
Microsoft hasn't published an API, yet. That should be coming with one of the next versions. |
Thanks for the prompt reply. As basic highlighting was all I'm really hoping for, I'll give your suggestion a shot, and close this issue. |
Do the latest changes work for you? Please reopen with comment if not. |
or comment directly on 4f73668 |
btw changes are untested, it's late at night here but wanted to publish early and move fast. |
@MarcusLlewellyn VS Code has left preview status and been released as beta. Extension support seems finalized, I'll be looking into updating the files next week as I'm busy this week. |
Are there any plans on creating an official VS Code extension, uploading it to the Visual Studio Marketplace? I might be interested in getting involved. |
Currently no plans from my side. Should you be willing to do that, FYI some links below:
What are your plans? I'd accept a PR to fix #19 and add lslforge support, should you want to start from there. |
First, thank you for the effort put into all of these file for so many different editors. It must be a titanic effort!
Just wanted to note that the LSL support files for Visual Studio Code don't appear to be working. I've tried it with versions 0.7.0 and 0.8.0. I appreciate that this editor is a moving target that is actively under development. I'm confident that I've copied the vs.language.lsl folder into the correct lo the correct location for both versions.
The text was updated successfully, but these errors were encountered: