I'm OK with the patch, but it makes configuration a bit more difficult since users should actually know all the alignable keywords. I guess we can mention `ruby-alignable-keywords' in the docstring
of `ruby-align-to-stmt-keywords' and consider this a good enough hint for the users. One problem with the current implementation is that it won't play nice with assignments if you won't to treat them differently:
x = def something
ala
bala
end
There won't be a way to get this indentations at the same time:
private def something
ala
bala
end
and
x = def something
ala
bala
end
I think that it might make sense to support a different def alignment for `def` after `private`, `protected`, `public` regardless of the `ruby-align-to-stmt-keywords' value. What I'm saying is that some people
might prefer to align `def` with a statement beginning only with access modifier methods. Of course, it seems unlikely that someone will assign the value of a method def to a variable, but in the future a method definition in MRI, but it makes sense in Rubinius for instance.