#Vscode atext extension how to#
#Vscode atext extension full#
#Vscode atext extension software#

The userland LSP package allows it to have a fast develop/release iteration and even if it doesn’t release a new tag, I can use the latest source from the Github repo.

I can’t image that what if I have to wait for kind of 1 month dev build or 4 months stable build to get a tiny LSP bug fixed (and ST says itself as a text editor. But even in userland implementation, it still take much effort to get it work well. Iirc, staff think it’s better to be implemented in userland.

Do you have plans to add native LSP support in next releases?.

This has been mentioned somewhere with staff’s reply (maybe in Discord). Phase 2 might be focused on bringing LSP and support to Sublime Text to improve autocomplete, syntax highlighting, etc

I’m not new to Python but I’m definitly new to ST plugin development.

#Vscode atext extension how to#

In the meantime, I will be trying to contribute to this awesome text editor by bringing Dart reformat support to vscode (I’m not 100% sure how to do it yet. I would also keep package control as another source of getting plugins for people who don’t want to mess with any vscode stuff (I know there are users that would use vanilla ST and I respect that).Įven if this is not done, I’m not going anywhere, however, I think these enhancements would mean a lot to a bunch of people who just want an editor that can help them on their day-to-day.

#Vscode atext extension full#

I would not even consider bringing debugging, etc to the mix, as I believe that is better suited for a full IDE and can hugely impact performance Users can always go to Tools > Developer > Profile Plugins to know why Sublime is slower, but I wouldn’t mind losing a bit of performance in order to gain a ton of functionality. Phase 2 might be focused on bringing LSP and support to Sublime Text to improve autocomplete, syntax highlighting, etc (I know this one will have performance implications, but most likely will still be faster than vscode).

#Vscode atext extension software#

Lately, I’ve seen a few instances were ST could benefit from implementing vscode extensions since there is no support or little support for certain languages due to relying mostly on the community to implement (I’ve seen that there are some text editors already doing this or planning to do so onivim extracted vscode extension host for their text editor).Īs an ST lover, I want the best for this software and the developers behind the product, and feel that by adding vscode extension support, you will be able to keep a good amount of people that are moving to the “new kid on the block”.įrom what I’ve researched, adding color scheme vscode extension support could be done in Phase 1 on an Alpha release, as vscode is using the same TextMate rules that Sublime Text does (you would be able to recover almost ALL of the themes that plugin developers abandoned when they moved to vscode. It’s snappier than vscode and even when I’ve been running both side-by-side for the better part of 3 years, I normally try to come back to ST when possible due to the performance difference in some big files I work on. First of all, I wanted to start by saying I love Sublime Text.