Are You using EditorConfig?

[Eiji]

@hauleth

For me it is irritating as the editor need to reload edited file after each save, which sometimes screw the undo (I have persistent undo in Vim enabled). Additionally it fires file watchers twice, so sometimes it can cause “wasted cycles” when running tests twice after each change.

Heh … what should I say … I recommend Sublime Text 3

I do not have a tests for each file change as it’s generally bad idea. It may be good for small bugfix, but in normal case (enhancement or new feature) which requires to add and/or modify many files it would cause unnecessary fails.

@hauleth

Additionally mix format will not work with files that aren’t UTF-8. While most editors use that by default it not always can be a case, for example Windows sometimes use UTF-16 which will crash the mix format :

It’s why I do not use Windows at all. They have their own standards. Look that people in France think that French is most important and everyone should know it, but it does not changes anything in typical daily English programming …

@hauleth

Yes, but it will not manage all files in projects. Erlang files or Makefiles will not be formatted via mix format . And if you configure tabstop option then GitHub will also show files in diffs and file display with proper indentation depth.

Well … Elixir was created for some purpose … If Erlang would have syntax, code, formatter and everything else from Elixir then Elixir would not be created.

But seriously … Makefile is good example, but it’s not like that it’s used in really big percent of projects. Erlang team could create formatter if they would like to. The better way is to create formatter for each language rather than implement support for all languages in each editor which is obvious waste of time.

As said Makefile is a different case, but it’s really one file and alone does not gives enough arguments to introduce a generic formatter.

@hauleth

The for me in EditorConfig is to make it pass before even being sent to the CI, as most of these “fixes” can be applied automatically by editor (proper indentation characters, indentation width, charsets, etc.). This is also handy for root = true option for a lot of tools, as this marks the “main” directory of the project and such tools can “stop” when traversing the directory tree in lookup for “root directory”.

This should be able to work with Elixir formatter. Of course not many editors know .formatter.exs, but there is really no need for that. That’s why many editors have support for plugins.