Brujo Benavides

This might be impossible to solve due to `ktn_dodger` not returning the text for the whole structure, for complex structures… i.e. when parsing `[1]`, the `text` property for the list...

In the same way as https://github.com/AdRoll/rebar3_format/issues/167#issuecomment-780650290 … `erl_syntax:subtrees/1` and other `erl_syntax` functions, like `list_suffix/1`, `cons_suffix/1`, etc… go to great lengths to hide the syntactic information to make stuff like `[1,...

Sadly… it's practically impossible, at least without replacing `prettypr` as our pretty-printer. I'll try to give you the best explanation I can come up with… `prettypr` expects a group of...

I added a link to this thread in the README, by the way.

This is related to #199.

I like it! I'm not sure how feasible this would be… considering what's discussed in #199 It might require a new formatter altogether.

Yes. This is a known issue. If you want to see something even funnier, try with multiple comments, like… ```erlang -type transaction_error() :: no_workers | not_owner % this one will...

It's related to #152

This can't be solved until `erl_syntax:attribute_arguments/2` quit messing around with node positions, i.e. erlang/otp#4529

I've been doing a little bit more digging into `prettypr`, but to no avail… It looks like those spaces are practically unavoidable. We might want to do one of these...