Gábor Csárdi

@brianmsm Well, these are things I might implement in the future, or things I am happy to get help with. What do you need from `memory_full_info()`? There is `ps_memory_info()` with...

@brianmsm Happening here: https://github.com/r-lib/ps/pull/122, Linux seems to be working well.

CPU affinity happening here, FYI: https://github.com/r-lib/ps/pull/123

Yes, this would make a lot of sense indeed. I agree that we would need to version the vault format to implement this properly. Maybe we do not need to...

No worries, no rush from my part. :) Let me know if you need feedback, you don't need a polished PR for a first iteration. Or if you have questions....

Yes, sry for the delay, in a couple of days!

FWIW, after tracking down a bug that involved debugging `rlang::.onLoad()`, I am not such a big fan of `on_load()`.

Grepping is fine, but I wanted to put a `browser()` in it to see what triggers the `package_version()` bug.

I wanted to step over all the stuff that happens in `.onLoad()`, so the `browser()` goes in `.onLoad()`. But then you step into `run_on_load()` and then each `callback()` is ```...

Ah, no need, I'll just get better at this... :D