Expr
A Sublime Text syntax for Expr
Details
Installs
- Total 3
- Win 1
- Mac 2
- Linux 0
| 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 | Aug 29 | Aug 28 | Aug 27 | Aug 26 | Aug 25 | Aug 24 | Aug 23 | Aug 22 | Aug 21 | Aug 20 | Aug 19 | Aug 18 | Aug 17 | Aug 16 | Aug 15 | Aug 14 | Aug 13 | Aug 12 | Aug 11 | Aug 10 | Aug 9 | Aug 8 | Aug 7 | Aug 6 | Aug 5 | Aug 4 | Aug 3 | Aug 2 | Aug 1 | Jul 31 | Jul 30 | Jul 29 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 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 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| Mac | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 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 |
| 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 |
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.