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