Elm Syntax Highlighting
Syntax Highlighting for Elm in Sublime Text
Details
Installs
- Total 29K
- Win 9K
- Mac 15K
- Linux 6K
Dec 22 | Dec 21 | Dec 20 | Dec 19 | Dec 18 | Dec 17 | Dec 16 | Dec 15 | Dec 14 | Dec 13 | Dec 12 | Dec 11 | Dec 10 | Dec 9 | Dec 8 | Dec 7 | Dec 6 | Dec 5 | Dec 4 | Dec 3 | Dec 2 | Dec 1 | Nov 30 | Nov 29 | Nov 28 | Nov 27 | Nov 26 | Nov 25 | Nov 24 | Nov 23 | Nov 22 | 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 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 0 | 0 | 1 | 2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 3 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 2 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Mac | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 2 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 2 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 2 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 |
Linux | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 2 | 2 | 0 | 0 | 1 | 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 | 1 |
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.