-
Notifications
You must be signed in to change notification settings - Fork 1
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
VS Code Support #3
Comments
Apparently, it's as simple as converting the CSON file to JSON and publishing it to VS Code's marketplace. A user documented the steps for me here, so there you'll find the steps involved in creating a port. =) As I stated on the aforementioned thread, I'd prefer a VS Code user maintain a port for my work than to be responsible maintaining packages for an editor I never use. |
Thank you very much for the information. I may attempt this myself; if so, I will absolutely refer it to the original repo here, as you asked in the other issue. |
How'd you go, mate? =) |
I unfortubately I didn’t get around to it. I’m using VS Code for a few things these days, things it does better than Atom (coding in Rust, for example), but Atom is still my preferred lightweight editor. I myself have made some Atom packages (trivial) and have yet to see what I would need to do to make them work in VS Code. |
Are you considering doing this now? |
Hello any news on this i would love to have the muse.cson file converted to be use for zed editor ^^ to have a cool extensions @JosephTLyons |
I'm not sure how hard or easy it would be to port this package over to VS Code, but I would love to have this package available there. I'm beginning to use VS Code alongside Atom these days and surely miss the Elisp syntax highlighting.
Also, forgive me if there already exists a package and that if one does exist, I simply missed it during my search.
The text was updated successfully, but these errors were encountered: