Gábor Csárdi

If the installed package has source references, then there is file + line information, I think.

E.g. covr walks the language tree and uses the source refs to for every expression, so I think it is possible to do it. Might not be worth it, though.

> Here's a link showing that mingw is in the PATH: [dfalbel/testrtools/runs/6798819503?check_suite_focus=true#step:4:12](https://github.com/dfalbel/testrtools/runs/6798819503?check_suite_focus=true#step:4:12) Which path component do you mean specifically?

I don't want to bring back `windows-path-include-mingw` for rtools42, because for rtools40 the right thing is not to update the path, even if this now defunct parameter is set to...

Seems to work well, will be in `@v2` soon: https://github.com/gaborcsardi/testrtools/actions/runs/3289868195

Thanks, I think we can do this easily is there is a good source of tribe names available.

Well the documentation says: > It must be an R expression in single quotes. So the correct form is ```yaml - uses: r-lib/actions/check-r-package@v2 with: error-on: '"error"' ```

Changing the syntax is breaking change, so we cannot do that now. We can certainly document it better, which is what this issue is about.

Thanks, makes sense. Do you want to submit a PR? No pressure. :)

> Are there differences in environment variables etc. between `r_session$new()` and `r_bg()`? Maybe, but you can print/save the environment variables in both and compare. Unfortunately it is challenging for me...