Paulo F. Oliveira

@tak30, just a heads up: it will (might?) not be available for previous `rebar3` versions unless the maintainers make it so. So if I'm running 3.12 and you expect 3.19+...

Yeah, I've seen `rebar3` in projects way too many times, and feel the same as you do. 🤣 You are right, though: it might be helpful, "from here on out,"...

> if you have a team of developers working on the same project it is nice to ensure all of them are using the same rebar3 version Just throwing something...

> Oh, is the issue that the message reads like what will be removed is `daemon` and `daemon_attach`? The wording could be improved to make clear that the renamed commands...

> I'm wondering if we should shift to that format only optionally, when we know we want a device to handle the output. I think this would be a good...

> following existing UX idioms in developer tools I, for one, consume the results of `rebar3 dialyzer` from the shell. Even if I do understand the output with all `:`...

(It also broke our CI, but yeah, we figured there was no turning back - and I kinda knew this was coming from previous comments...). As an example... Our CI...

Should this issue be closed?

Have you tried `rebar3_lint` (https://hex.pm/packages/rebar3_lint)? It's `elvis_core` under the hood and maintained by the same developers. (and @ferd is right, the name changing was unfortunate; it broke some expectations). For...

From my experience: 1. if `unknown` is not set, it'll not be used, 2. if it is set, it'll be used. (all good here). Is the expected behavior to have...