Davis Clark

agreed, but I don't see a reason to ever allow formatting an entire html file without a selection (feel free to correct me if I'm missing something though). Ideally, we...

@M4urice I think I'm ok with that. It also solves the problem of quickly formatting some throw-away content being a 2-step process (set syntax, format).

@pokocat I'm thinking maybe we just always allow the command palette option to show up, regardless of syntax.

looks good. As soon as we get #79 finished up I'll merge this in.

Promise I haven't forgotten this. I branched off from your pull request and added some more functionality to it; haven't pushed up to a feature branch yet though. Trying to...

@owenleonard Alright, I know this is ridiculously late, but have a look at the changes in the [plugin_activation](/jdc0589/JsFormat/tree/plugin_activation) branch. I took what you started with and added a few more...

@jackocnr it's not merged in yet, mainly because I've been a bad project maintainer lately and forgot about it. [mite-node](https://github.com/jdc0589/mite-node) has been taking up a lot of my free time...

@mokkabonna I'm a little bit out of the loop here...but what projects actually use the html css sections? What is the source of truth for the file spec?

Im with you now. Dug around a little and it looks like [this is the 'official' .jsbeautifyrc spec](/einars/js-beautify/blob/master/js/config/defaults.json). I don't think I am opposed to supporting the Sublime-HTMLPrettify .jsbeautifyrc format...

+1. Super useful when you want to clean up a few lines but aren't at a point where you can commit whitespace changes to everything else.