Lisplog

Blogging in Lisp

Search

Feed Aggregator

Rendered on Fri, 23 Aug 2019 08:32:07 GMT  newer latest older 
Next udpate: Fri, 23 Aug 2019 09:00:00 GMT feeds

Improving data structure diff in elm-test

via Elm - Latest posts by @system system on Fri, 23 Aug 2019 07:24:01 GMT

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

Ideas for improving editor experiences

via Elm - Latest posts by @KasMA1990 Kasper on Fri, 23 Aug 2019 07:06:08 GMT

I like the idea, though the specifications should be careful with being platform dependent. For example:

MUST run elm make --output=/dev/null --report=json $CURRENT_FILE_PATH from $CURRENT_FILE_DIR.

should use a command ala elm make --output=NUL --report=json $CURRENT_FILE_PATH on Windows.

Ideas for improving editor experiences

via Elm - Latest posts by @pdamoc Peter Damoc on Fri, 23 Aug 2019 06:41:26 GMT

I think this is the crux of the issue with a lot of plugins.

For my personal preferences, when I start with a new language I just want to be able to build the simple “Hello World” file from the editor. I code a little, build, change, build, change, etc. It is a conversation with the compiler and I don’t want to have to leave the editor for this. I view this functionality as a MUST for absolute beginners. When I was starting out, this was the reason why I chose SublimeText over Atom. I could not figure out how to make Atom build on demand.

In my perspective, the syntax highlight, elm make and elm-format belong in a single “Elm support” plug-in. The only configuration for this plugin would be the elm-format on-save toggle which could be false by default to not confuse absolute beginners.

The problems like bad performance, battery drain and fighting with the autocomplete come ONLY when you bring in project analysis. That should be delegated to an advanced support plugin.

 newer latest older