Add Move Language Package to Package Control

[WhiteRabbitGithub]

• I'm the package's author and/or maintainer.
• I have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax, it doesn't also add a color scheme. ***
• My package is named after the language it supports (Move), without suffixes like "syntax" or "highlighting."
• I use .gitattributes to exclude unnecessary files from the package (e.g., images, test files, .sublime-project/.workspace).

---

About the Package

• Name: Move Language Package
• Repository: https://github.com/SonicSnipeBot/sublime-move-language
• Description: This package provides syntax highlighting and LSP support for the Move programming language in Sublime Text.
• Key Features:
  • Syntax highlighting for .move files.
  • Language Server Protocol (LSP) integration using move-analyzer.
  • Auto-completion, diagnostics, and code navigation features.

Why Add This Package?

There are no existing packages in Package Control that provide syntax highlighting or LSP support for the Move language.

---

[braver]

Couple points here.

Please separate the LSP support into a different repo and submit it here to be added to package control: https://github.com/sublimelsp/repository. That community manages everything related to LSP. And users expect syntax packages to be separate from LSP packages (at least in the Sublime world).

So your entry here should just be for the syntax itself. “Move” or “Move Language” would be good names (all packages in package control are packages so they don’t need package in their name 😉).

It looks like the LSP is deprecated though, is there a newer version?

Your syntax file should not have the yaml extension.