Closed ghost closed 6 years ago
Thanks for the testing. Yeah, this all falls into the "expressions like this" category that I mentioned in my comment you refer to. To be more precise, these are expressions with infix operators (=, orelse, andalso, ||) that are broken into multiple lines without extra parentheses.
Closing due to inactivity.
I’d like this to be kept open as this is a fairly frustrating shortcoming if the indent support. On Thu, 31 May 2018 at 13:26, Tuncer Ayaz notifications@github.com wrote:
Closing due to inactivity.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vim-erlang/vim-erlang-runtime/issues/32#issuecomment-393500197, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlFKulmXepQOA6M0Go4eT0ndqg7cWks5t39N5gaJpZM4Hq1iq .
if you close your eyes, it won't solve the problem. Please consider adjusting the indent, second case is really frequent and annoying in wild life.
Since vim-erlang is designed to follow erlang-mode indenting style (see https://github.com/vim-erlang/vim-erlang-runtime/issues/31#issuecomment-189942651), I did a quick test of some of the rebar code.
rebar_port_compiler:os_env/0:
erlang.el:
vim-erlang:
diff after vim-erlang indent:
rebar:set_log_level/3:
erlang.el:
vim-erlang:
diff after vim-erlang indent:
rebar:is_command*:
erlang.el:
vim-erlang:
diff after vim-erlang indent: