-
Notifications
You must be signed in to change notification settings - Fork 0
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
1.1.0 appears to break ST3 compatibility #46
Comments
Thanks. Fixed in 1.1.3. |
Thanks for your quick response. Just removed 1.0.15 from the Package folder and uninstalled lsp-css and, installed 1.1.3 via the package control, restarted Sublime and got this new error:
|
That looks like we need to make a legacy branch for ST 3. |
Looks like 1.0.19 is working fine.
…On Sun, Nov 26, 2023 at 10:38 AM Jack Cherng ***@***.***> wrote:
Could try whether 1.0.19 works for ST 3?
—
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJVXUYUYLLUDJEBGC3LMPTYGMEZRAVCNFSM6AAAAAA72NABT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWG4ZTKNZRGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
juliangarnier.com
|
Also noticed the same type of error in lsp-json :
I'm afraid this error is related to a change introduced to a lot of languages... |
Yeah. I think no one among LSP devs still uses ST 3. |
They have been not working for ST 3 for quite a while actually... sublimelsp/LSP-css#46 sublimelsp/LSP-html#45 Signed-off-by: Jack Cherng <jfcherng@gmail.com>
They have been not working for ST 3 for quite a while actually... sublimelsp/LSP-css#46 sublimelsp/LSP-html#45 Signed-off-by: Jack Cherng <jfcherng@gmail.com>
Understandable, the only reason I'm still using ST 3 is because ST 4 has worse performances for the type of work I'm doing, at least on my current machine. |
I would suggest reporting performance issues to https://github.com/sublimehq/sublime_text LSP functions much better with the Sublime Text 4 API. Some LSP features don't work well or are buggy due to API limitations in ST3. |
Already reported here sublimehq/sublime_text#6199 (comment). |
Closed since |
Hi, I just posted a similar issue for the LSP-html plugin at LSP-html GitHub Issue #45, which seems to be related.
I'm using ST 3211 and it looks like LSP-css is incompatible with ST3 since 1.1.0.
I installed LSP-css via package control, restarted Sublime and got this error in the console:
Manually downloading 1.0.15 to my Packages folder fixed the issue.
I know that ST3 is probably not your priority, but wanted to surface this issue just in case you didn't noticed.
Thanks.
The text was updated successfully, but these errors were encountered: