Elm Syntax Highlighting
Syntax Highlighting for Elm in Sublime Text
Details
Installs
- Total 29K
- Win 9K
- Mac 15K
- Linux 6K
Nov 21 | Nov 20 | Nov 19 | Nov 18 | Nov 17 | Nov 16 | Nov 15 | Nov 14 | Nov 13 | Nov 12 | Nov 11 | Nov 10 | Nov 9 | Nov 8 | Nov 7 | Nov 6 | Nov 5 | Nov 4 | Nov 3 | Nov 2 | Nov 1 | Oct 31 | Oct 30 | Oct 29 | Oct 28 | Oct 27 | Oct 26 | Oct 25 | Oct 24 | Oct 23 | Oct 22 | Oct 21 | Oct 20 | Oct 19 | Oct 18 | Oct 17 | Oct 16 | Oct 15 | Oct 14 | Oct 13 | Oct 12 | Oct 11 | Oct 10 | Oct 9 | Oct 8 | Oct 7 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 2 | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 2 | 0 | 1 |
Mac | 0 | 0 | 0 | 2 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 |
Linux | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Elm Syntax Highlighting
Just add syntax highlighting for Elm.
Install Instructions
Recommended Workflow
I do all of my Elm development with Terminal and Sublime Text open next to each other like this:
I mostly focus on the code in Sublime Text.
When I am curious if things work, I switch to Terminal and run something like elm make src/Main.elm
to see if I get any errors.
Then I switch back to Sublime Text and use Ctrl-t (or Cmd-t on Mac) to navigate to the relevant files and make any fixes.
Workflow Benefits
The recommended workflow has some underappreciated benefits:
- Fast - Never wait for a slow editor. No background tasks eating RAM and CPU.
- Flexibile - Some projects needs more than an
elm make
call. I can switch toelm reactor
or a custom./build.sh
script and keep essentially the same workflow. - Robust - Not much can go wrong here, so I never spend time messing with integrations. Changes in
elm
,elm-test
, orelm-format
are only a concern in the terminal.
I really love this balance! It has that particular character of focused designs.
That said, I know some people want a bit more, so I made elm-format-on-save
as well. It may be worth setting this up once you have been happily using Elm for a while and become curious what it might be like to use Elm at work.