Bozhidar Batsov

> I've always personally used the "template" style and I wonder why we have to worry about these suffixes and alternate format? Simply because I felt this resulted in the...

Well, it helps you figure out the types of the other arguments for `format`, but it's obviously subjective weather that adds value or not. I agree that the names are...

I don't have a strong preference, but as the users are not complaining I'd rather not introduce any headaches for them, by changing the default. That's my only consideration. If...

Interesting. I didn't even know this was possible. I wonder how well most editors handle it, though.

While I don't mind changing this for RuboCop itself (unless someone from @rubocop/rubocop-core objects), that's a breaking configuration change we can't do before 2.0.

> If my understanding that it's better to release 2.0 soon is correct, I intend to continue with the few remaining 2.0 issues. I'm not opposed to doing major releases...

We can just create a branch named `rubocop-2.0`. :-) My only concern with this is who's going to be keeping it in sync with `master` - I assume there are...

Perhaps this can be added to the `LineLength` cop as some option, as it already breaks down long arrays. I just don't recall how exactly did it split them.

Yeah, something like this has been on my mind for a long time now. The current way we do things is simply a remnant of the very early days of...

I guess we can revisit this after @Darhazer is done with the metadata epic, as those are somewhat related. That might also remove the need for inline documentation of the...