-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Array indentation seems broken #33
Comments
@lunaryorn sounds right, thanks. |
@j0ni You're welcome! Please report any other indentation flaws you find. While we won't fix them immediately, they show us what we need to look for when implementing SMIE. |
@lunaryorn This particular SMIE code can be borrowed directly from ruby-mode. I guess we'll be able to borrow from them heavily given the fact that the puppet lang shares some common ground with Ruby. |
@bbatsov I hope so. I actually made my living here by borrowing from Ruby Mode. The string expansion stuff is also conveniently stolen from Ruby Mode ;) |
I’m well aware of that. :-) I’ve been following @dgutov’s work on ruby-mode closely over the past year or so. He’s one of the best hackers in the community, so borrowing from his work is always a good idea. One can certainly do much worse. :-) Cheers, On Friday, March 14, 2014 at 8:00 PM, Sebastian Wiesner wrote:
|
@bbatsov Yeah, indeed. It's a well-written mode, and there's a lot to learn from it. |
😊 Thanks, but ruby-mode still has its share of warts. There's old indentation code left, a few commands still use it even with SMIE integration enabled, and the SMIE grammar is far from perfect, making the indentation code in places more complex than is probably has to be. Sexp movement is also not always intuitive because of that. |
Aw, just saw this after fixing this indentation locally. Can I convince you to accept a pull request addressing this while you're working out the details of SMIE? |
Multiline array literals get formatted like this:
which seems quite broken. I think they should look like this:
The text was updated successfully, but these errors were encountered: