Elm.tmLanguage
Elm.tmLanguage copied to clipboard
Elm language syntax highlighting and tool integration for ST2/3
It would be nice to report the syntax error from elm-format, rather than the current silent no-op.
It looked like this plugin was broken, but then I installed sublime text 3 and all the advertised features (type panel, elm-format, etc) started working. I have elm-format, reactor, repl,...
The following results in the 'd' in `Vector3d` being highlighted in red: ``` module Vector3d (..) where ``` `Vector3` and even `Vector3D` work fine.
Is there a way to turn this off, or somehow integrate [this package](https://packagecontrol.io/packages/ANSIescape) into the build? [This issue](https://github.com/aziz/SublimeANSI/issues/1#issuecomment-94841695) seems to have some hints, but `target` and `syntax` are already defined...
Currently, building (not running) only executes elm-make command on the current file. It does not respect if you have set the main field in elm-package.json. It would be great if...
Since the compiler generates warnings with suggestions for type annotations, the plugin should offer the option of automatically inserting them. (Similar to Alt-Enter quick-fix on InteliJ IDEs)
When my build code compiles without errors I see the following message at the top: ``` === Successfully generated /dev/null === [Finished in 0.4s] ``` I know this [reason](https://twitter.com/rtfeldman/status/624026168652660740) for...
Hello, When starting sublimetext 2 I got the following error: ``` Traceback (most recent call last): File "./sublime_plugin.py", line 62, in reload_plugin File "./elm_show_type.py", line 133 for v in data...
The new way to install the beta version is to open the Command Palette and select `Package Control: Add Repository`  Then you enter the following and press Enter: `https://raw.githubusercontent.com/deadfoxygrandpa/Elm.tmLanguage/beta/beta-repository.json`...
Right now, if you import a module as another name, it confuses elm-oracle. I can parse import statements on my own and work around this to make the behavior correct.