Use do...end as code block delimiters

[kelvinst]

The current behaviour is considering only some keywords as block delimiters, like defmodule...end or def...end. I'm guessing this according to this behaviour in my delimiters highlighting:

Well, the behaviour I was expecting is hightlighting the do and end keywords, and not the definition ones.

My understanding goes this ways because in elixir, the block delimiters are actually do...end, which is actually just a syntax sugar for do: (...).

[kelvinst]

PS.: fn...end is also a block delimiter.

[kelvinst]

PS2.: I don't really know if this should be an Issue here or in smartparens, but I had to open it somewhere.

[kelvinst]

Nevermind what I said, updated my packages and it's pretty much working now. 😬

I say "pretty much" because I'm still having problems with try do ... end blocks. Are you aware of it?

[onelesd]

You could use evil-matchit, which is more general purpose and useful. It handles try do ... end fine.

[art-solopov]

I'm still having issues on functions that don't use do ... end syntax and instead use just the do: (...) expression.

[mogorman]

I am having the issue where end is not auto inserted for def, defp or defmodules, Also it is not matching the end, like it does with case and if blocks

[opie4624]

This also manifests if your function or module names start with the word end.

[nicobao]

Hi! Here is another example where similar errors occur in Elixir: with the quote do.. end construct.

Note sure whether it is related to this smartparens issue?

If someone is ready to provide some initial guidance, I'd be happy to help.