lassik

> See the Preinstalled column of https://github.com/Glavin001/atom-beautify#beautifiers That table is very impressive. In fact, it was one of the original inspirations for the Emacs package :) I also mainly use...

Strongly agree. There was some related work in Unibeautify core a while ago: https://github.com/Unibeautify/unibeautify/pull/152

Avoid having to pass `--language foo` manually. It would be convenient and I can't think of any harm it would cause.

This refactoring came up with the Windows work, but I decided to make a separate PR about this. That way we get a clean PR and commit about this cross-platform...

The shell script is called `.travis-codeclimate.sh` with a leading dot because `.travis.yml` also starts with a dot. Should it be called just `travis-codeclimate.sh` without a dot? Looks kind of ugly...

Removing all the error checking and clarifications (well, they were clarifications to me anyway 😄 ) it would look like this: ```sh #!/bin/bash os=$(uname | tr '[:upper:]' '[:lower:]') [[ $os...

Thanks :) Maybe we should get a third opinion from @Glavin001. I took Windows into account - the line `[[ $os =~ (darwin|linux) ]] || exit 0` exits right away...

Ah, you meant adding Windows to `.travis.yml` rather than the shell script. I thought I'd do that in the original Windows PR #95 and just spin off this one to...

OK, rebased. The main reason I'd like to gather all the Windows porting work in the Windows PR is to keep the log of all errors encountered in one PR's...

Continuing from #95 which we considered too messy at this point.