Bump vscode-textmate-languageservice from 0.2.1 to 1.1.0

[zm-cttae-archive]

This is a full rewrite of the library that kills all tech debt, perf issues, and also adds browser support.

All providers exit within 100ms except for the definition provider which takes 1200ms. Not perfect but we've cut overheads by 1-2 orders of magnitude!
3 running theories for improvements.. mainly putting a stack variable for variable-property text merging in the tokenizer, & coalescing output data further to kill any overhead.

Not sure we are at the finish line here, but this will close a bunch of issues for sure.

These issues had regression test cases built to test them.. definitely killed these bugs 😄

• Closes Performance issues with folding #157.
• Closes if, else, end one liners disrupt the outline #159.
• Closes Lag typing large file with Matlab extention #162.
• Closes This extension keeps crashing the Extension Host #165.
• Closes Extension Host Terminated unexpectedly #168.
• Closes Extremely slow: Go to Definition F12 or Peek Definition #172.
• Fixes Go to definition is not working #147.
• Fixes ctrl+click to open function not working in 2.2.0  #143.
• Fixes Extension v2.3.0 becomes unresponsive #152.

If the changelogs interest you... 1.0.0-rc-1 and 1.0.0-rc-2

[zm-cttae-archive]

Testing: extension is fully tested (vsce package) on my local machine, and via npm test against the library's test suite.

If you would like browser support, we can now enable it. But we'd need to conditionally kill features

[jankap]

This is awesome! Big question: will @Gimly merge this or not in the future? Can I try this out on my PC already?

[zm-cttae-archive]

Run it in PWSH for Windows or your bash console on Unix:

$ cd ~/.vscode/extensions/gimly81.matlab-2.*
$ npm i [email protected]

[zm-cttae-archive]

Shoot... you will have to clone this out, npx vsce package then install the VSIX file.
https://gitlab.com/SNDST00M/vscode-textmate-languageservice/-/blob/main/CHANGELOG.md#100-rc-1

"Significant changes to the shape of the API exports."

[jiecui]

Huge thanks!!
However, after upgrading to 1.0.0, mlint does not appear to work anymore.

[zm-cttae-archive]

Did you upgrade via npm i, or did you clone my repository and rebuild the extension? There are some changes to the way the LSP is initialised.. hopefully for the last time but yeah

[zm-cttae-archive]

Hack to fix vscode-matlab performance for yourself

Put all these commands in the console:

$ git clone https://github.com/Gimly/vscode-matlab.git
$ cd vscode-matlab
$ git submodule update --init
$ npm install npm-run-all --save-dev
$ vsce package
$ code --install-extension matlab-2.3.1.vsix
$ cd ..

(Colourization is fixed in the snippet now)

[jiecui]

Sorry for the late reply. Thanks a lot for the comments!
All the above commands were executed successfully, but mlint problem persisted. In addition, the editor also lost colorization of some of the code. I switched to Matlab extension older version v2.0.0, which works all right.

[zm-cttae-archive]

I am downloading a fresh purchased copy of Matlab to debug today

[zm-cttae-archive]

Works for me:

[jiecui]

Thanks! Probably, the issue is at my end. How can I remove Xavier Hahn's Matlab extension completely and try a fresh start?

[zm-cttae-archive]

code --install-extension matlab-2.3.1.vsix should have done it 🤔

[jiecui]

Still doesn't work well for me after a complete re-installation, but I guess the issue should be at my end. Thanks anyway!

[zm-cttae-archive]

We now have web support! Better than Anycode 🎁❣

[zm-cttae-archive]

@jiecui go to github.dev/jiecui/mpact - please install [EXPERIMENTAL] Matlab extension and try it.

[jiecui]

Nice!

[eluum]

I have not been able to get this working for vscode on windows, seems like I have the same issue as @jiecui based on his screenshot. Building and installing the package from the cloned repo doesn't seem to work, using the version in the vscode extension Marketplace works but lags too much to be usable.

[zm-cttae-archive]

Riiight.. you've got to do git submodule update --init to have the grammar.

EDIT: I updated the comment w/ instructions for local fix - #174 (comment).

---

@Gimly you'll need to do npm i npm-run-all --save-dev and commit the new dependency to fix the build..

[eluum]

Thanks, everything is working now. Great job making this extension usable!