Nix
Nix syntax highlighting for Sublime Text
Details
Installs
- Total 5K
- Win 456
- Mac 2K
- Linux 3K
| Apr 22 | Apr 21 | Apr 20 | Apr 19 | Apr 18 | Apr 17 | Apr 16 | Apr 15 | Apr 14 | Apr 13 | Apr 12 | Apr 11 | Apr 10 | Apr 9 | Apr 8 | Apr 7 | Apr 6 | Apr 5 | Apr 4 | Apr 3 | Apr 2 | Apr 1 | Mar 31 | Mar 30 | Mar 29 | Mar 28 | Mar 27 | Mar 26 | Mar 25 | Mar 24 | Mar 23 | Mar 22 | Mar 21 | Mar 20 | Mar 19 | Mar 18 | Mar 17 | Mar 16 | Mar 15 | Mar 14 | Mar 13 | Mar 12 | Mar 11 | Mar 10 | Mar 9 | Mar 8 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 2 | 0 | 1 | 0 | 0 | 2 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 0 |
| Mac | 0 | 1 | 2 | 0 | 0 | 1 | 1 | 0 | 1 | 0 | 2 | 2 | 2 | 2 | 1 | 2 | 1 | 0 | 1 | 2 | 1 | 3 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 3 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 2 | 0 | 2 | 0 | 1 | 1 | 0 | 2 | 0 |
| Linux | 0 | 2 | 2 | 1 | 3 | 4 | 0 | 2 | 1 | 3 | 5 | 4 | 1 | 2 | 2 | 1 | 1 | 2 | 3 | 1 | 3 | 0 | 1 | 1 | 0 | 1 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 0 | 1 | 0 | 2 | 2 | 0 | 0 | 1 | 2 | 1 | 1 |
Readme
- Source
- raw.githubusercontent.com
sublime-nix
Nix syntax highlighting for Sublime Text.
This syntax tries to be complete, and marks illegal code as such.
Unfortunately, the syntax highlighter in Sublime Text does not implement a full state machine and therefore this is an approximation of the actual syntax Nix allows. It's a bit looser and will mark things as illegal in corner cases.
Specifically, it has to guess whether { starts an attribute set or a function call, and it can't look ahead to the next lines, so it allows both until it's sure. However, this means that on column 0 the expression end-condition can match on a , or } and this breaks the syntax highlighting. As soon as it is sure of one or the other, this no longer applies. So this is only applicable to empty {} and comma-first function calls on column 0, not a big problem.
Tested against the nixpkgs code and the Nix test suite, it seems to render those ok.
There is some fun code in here, approximating a proper parser by recursing into rules with end conditions matching end of expression.