News for hackers. Stuff that matters.

A comment on EditorConfig. Parent comment

Re:EditorConfig by rstacruz on Thursday October 16, 2014 @01:48AM (#8463557)
Typically those are done using configuration files of code-checking tools, such as .jshintrc[1] or .pylintrc.

[1]: https://gist.github.com/connor/1597131

[ Parent | on HN ]
Re:EditorConfig by canadev on Thursday October 16, 2014 @05:33AM (#8464096)
I guess I just figure these two are sort of overlapping. If you use .jshintrc why do you need this tool?

(The neat idea being: if a project has many languages, you can share code conventions for all of them in one place.)

[ Parent | on HN ]
Re:EditorConfig by michaelmior on Thursday October 16, 2014 @09:21AM (#8464705)
The nice thing about EditorConfig is that it fixes some problems before they occur instead of requiring you to manually fix things after running a linter (e.g. spaces vs tabs)
[ Parent | on HN ]