Andrew Radev

Unfortunately, it's impossible to solve this right now, without a significant re-thinking of how we handle these kinds of line continuations :(. This issue is similar to (the very old)...

The alternative (working) way is, well, working :). If you have vim-ruby installed, it should indent hashes like that out of the box. You can indent code using the `=`...

@smackesey For me, this example seems to indent correctly: ``` ruby { 'a' => { 'b' => { 'c' => 'd', 'e' => { 'f' => 'g' } } }...

I can't seem to reproduce the issue on the current master branch. Could you check if you've got the latest version from github? If you do, it might be something...

@klieth Could you also post your .vimrc? The particular settings you have might give me a clue.

Hmm, well, I tried installing this distribution. It was harder than it should be, since the authors seem to be building it exclusively for MacOS (relying on the presence of...

All tests seem to pass for me, so I can confirm this commit doesn't seem to break any of them, at least. Can't really tell why they're not working for...

I'm sorry it took so long to respond to this issue. It slipped through the cracks, somehow. You're right that it takes a ridiculous amount of time to indent this...

I like the _idea_ of moving to a standard, myself, but I wish this wasn't the standard. From what I can see from the instructions, all the examples need to...

``` ruby # START_INDENT foo.bar(). # END_INDENT # START_INDENT baz() # END_INDENT ``` If the tests run `=` only on the bracketed lines, group by group, the second one would...