Gábor Csárdi

Seems like processx will use the default code page, unless the console is inherited: ```r > processx::run("chcp")$stdout [1] "Aktive Codepage: 437.\r\n" > processx::run("chcp", stdout = "")$stdout Aktive Codepage: 65001. ```

Per https://serverfault.com/questions/80635/how-can-i-manually-determine-the-codepage-and-locale-of-the-current-os/836221#836221 we can get the code page(s) from the registry, both for command line apps and for old gui apps. OEMCP could be the default for processx, although that...

I am afraid that there is no way to do that currently.

It is unlikely that we would implement this in remotes, but we could implement it in pak.

I am sorry, I am not sure what you mean.

> Is there any chance this is possible in future releases? As we are focusing on pak, we are not adding new features to remotes, so it is unlikely. >...

> what I still don't get is the link between the pak package and this [vignette](https://remotes.r-lib.org/articles/dependencies.html). Is pak:pgk_install able to make use of Remotes in a packages DESCRIPTION file? Yes:...

Yes, AFAICT that should work, provided that you have the credentials to access these repositories in the git credential store, and you are not running into this bug: https://github.com/r-lib/pkgdepends/issues/319

Reprex, no output: ```r library(cli) options(cli.progress_show_after = 0) { cli_progress_bar(total = 1, clear = FALSE) cli_progress_update() } ``` Correct output for two steps: ```r { cli_progress_bar(total = 2, clear =...

TBH IDK how useful it is to show a progress bar that has a single step. But I agree that some consistency would be nice. Right now, the finished progress...