0x5c

Piping the output to a pager breaks the commands that require user-input. As for the need for this to be implemented, it isn't. This is would be a user experience...

> this is why -y exists, to avoid interactivity But that makes it impossible to review changes before applying them.

Piping to less simply does not work, all that is shown is the repo update lines and the (broken) yes/no prompt. It also is a broken input state where you...

> The part before the confirmation prompt does not fit in the scrollback? Didn't know it could be that much (but I'm also quite new to void). For normal (frequent)...

Any updates on this? I'm using docopt a lot, but it has *tons* of issues, and has been seemingly abandoned, so this fork seems like the solution moving forwards. Except...

That is good news! I'll keep docopt-ng in my toolbox then. However, I am not comfortable with receiving undue credits, and especially for making PRs, so let's redirect that in...

I'd be interested in adopting `geteltorito`, `stlink`, `urh`, and `f3`

I'm also interested in adopting `libpwquality`

> Does this inject a bunch of control characters into the raw output from GitHub CI? Yes, Github uses standard ANSI escape codes to render colours in the output, so...

What remains to be done?