Konrad Rudolph

> I just enjoy being able to use the __init__.r script and it feels odd to me that we cannot use these on scoped projects. I’m not sure what you...

> I hope this clears things up. It does, thanks. I still haven't decided how to best tackle this feature request but I will add _some_ way of using unscoped...

Apologies for the radio silence, it was a combination of life happening and me having issues with my computer which lead to my dev environment crashing constantly. Anyway, please have...

Thanks for the report, I can confirm that this is a bug. Unfortunately I am not sure that it will be easy to fix, since the way reexports are currently...

Hmm. This is actually more complex than I thought. Consider the following module `a.r`: ``` #' @export box::use(./other_mod[alias = name]) ``` If a user now imports `a` and runs `box::help(a$alias)`,...

Apologies, I’ve no idea why I didn’t initially post it as one. ```r writeLines( c('A,B,C,D', 'foo,bar,"ba', 'z,bat'), 'x.csv' ) vroom::vroom('x.csv', show_col_types = FALSE) #> # A tibble: 0 × 4...

Maybe in a similar vein (or should this be a separate ticket?), it would also be great if `rig run` had a `--script` argument (or similar) to run `RScript` instead...

Done. See #199.

The benefit/difference is that Rscript doesn’t echo the executed code, so it behaves like most other mainstream scripting language interpreters in non-interactive (`perl`, `ruby`, `python` …) in this regard. I...

Regarding the `-q` option: the most important use-case for `Rscript` is probably in shebang lines of executable scripts: (for reasons I don’t understand) shebang lines limit the number of arguments...