Brujo Benavides

> I have to imagine that whatever vsn gets installed by gleam is wrong... the escript references "erl10.0" - is that right? No idea. @paulo-ferraz-oliveira do you know?

Nice idea, but I will likely be more akin to… ```erlang -format begin_ignore. … -format end_ignore. ``` …or some other attribute-based solution like… ```erlang -format_block #{inline_items => false}. … -format_block_end....

I just figured out why we can't do this. In Erlang… you can't insert custom attributes after the first function declaration. That would mean we need to rely on comments...

I think I'll first ask around in Slack…

Yeah. Our goal is the same. I prefer attributes to comments just because comments can be introduced… basically… everywhere. With attributes is _clear_ that you can't put that thing _within_...

On this topic: erlang/otp#5689

# 💡 Ideas from Slack convo with @hauleth and @plux 💡 1. Before erlang/otp#5689, we can add stuff like… ```erlang -format #{ignore => [this_function/1, this_function/2, this_function_with_any_arity, this_attribute, …], …}. ```...

This comes from WhatsApp/erlfmt#135

Same issue as in https://github.com/AdRoll/rebar3_format/issues/167#issuecomment-780650290

Thanks for the report, @rlipscombe … It's likely related to #74 and #216. Macros with code in them are generally a pain point for the formatter. :trollface: Also for code...