David Barnett

Filed the proposal to inherit vim's 'shiftwidth' and 'textwidth' settings as #27. For this issue, it's still worth considering some kind of support for custom autopep8 args.

Going with `formatter_args[]` sounds good to me. We will want a non-global version since it can vary project-to-project which args you want. Probably still keyed off the formatter name, like...

Yeah, no progress yet. =(

Having two partial formatters for C++ might mean people would want #44 so you could run this include sorting and clang-format on the same source code.

Looks like clang has a sortIncludes option now. Does it sort includes how you want it automatically now, or would we need to explicitly configure something to enable it?

BTW, fine-grained range formatting will be really annoying for formatters that don't natively support ranges, like gofmt. The hacks we use to approximate range formatting will show errors if the...

Ugh, this is why all formatters should just have good range formatting support… I think I agree the fallback should be to format the whole file (only if the file...

+1 Related: I'm considering an alternative API for formatters (#14) where codefmt passes a handle in and the formatter can perform operations on it more flexibly. It's possibly overkill but...

Someone also suggested rubocop in http://www.reddit.com/r/vim/comments/2uab1g/codefmt_a_plugin_for_formatting_code_using/co9pn5e. Wonder how it compares to ruby-beautify…

Thanks! > Removed autocmd from mappings file, PTAL Looks like the autocmd is still in the mappings file? I'd suggest to instead restructure a bit to define a `codefmt#SetFormatExprIfAvailable` and...