Expr
A Sublime Text syntax for Expr
Details
Installs
- Total 5
- Win 2
- Mac 3
- Linux 0
| Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | Oct 6 | Oct 5 | Oct 4 | Oct 3 | Oct 2 | Oct 1 | Sep 30 | Sep 29 | Sep 28 | Sep 27 | Sep 26 | Sep 25 | Sep 24 | Sep 23 | Sep 22 | Sep 21 | Sep 20 | Sep 19 | Sep 18 | Sep 17 | Sep 16 | Sep 15 | Sep 14 | Sep 13 | Sep 12 | Sep 11 | Sep 10 | Sep 9 | Sep 8 | Sep 7 | Sep 6 | Sep 5 | Sep 4 | Sep 3 | Sep 2 | Sep 1 | Aug 31 | Aug 30 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Expr syntax for Sublime Text
This package contains a Sublime Text syntax for the Expr language. It is only available for versions of ST equal or newer to 4075.
The syntax was generated using Expr's language definition and the parser/lexer code as of commit 4b31df.
Installation
Most users will want to install via Package Control, where the package is named “Expr”.
Contributing
This syntax was generated by AI, using this custom harness to write tests. That means syntax tests are duplicated across two places:
- yaml_tests: These are AI inputs. The harness translates them to sublime syntax test files.
- tests: These are sublime syntax test files, added manually or via conversion from the YAML tests.
A file like yaml_tests/foo.yaml generates a corresponding tests/syntax_test_foo.
Experienced syntax writers are welcome to contribute as they usually would, ensuring their changes include new tests. It is fine to only write sublime syntax tests, just make sure there is no clashing in the names. If you want to make an edit to the existing syntax tests, you will need to adjust the corresponding YAML test and re-generate them. Sorry!
AI contributions are accepted, with some caveats: - It is very strongly recommended you use the linked harness/SKILL to set up your environment for developing. - PRs must have sufficient testing coverage for new changes and passing regression tests. Old tests must be passing and may only be adjusted when they were incorrect or incomplete. Removing other test cases would indicate you've introduced a regression. - Please use capable models. The first version of the syntax was generated with Opus 5.