Closed MichaelChirico closed 7 months ago
Traced down to how {processx} behaves and filed an issue there:
https://github.com/r-lib/processx/issues/386
Given the root cause, it may be up to {pkgbuild} to decide whether this behavior is working as intended & possibly document it, or else be careful to restore state on exit.
downstream fixed, nothing to do here
Copied from https://github.com/r-lib/pkgload/issues/272
In
R --vanilla
Is that intended/unavoidable behavior? It may harm reproducibility. OTOH, I can't think of a place where this causes an issue, it's just something I noticed when tinkering around on another problem. So don't feel obligated to devote too much effort to this.