Thats a variant of http://trac.sagemath.org/ticket/14243
In a self-contained build of Sage you probably don't want the bundled R to break just because the user also has a different version of R installed with incompatible config files A system-wide install of Sage should have R using the usual config files. On Sunday, November 1, 2015 at 1:27:10 AM UTC+1, Andrey Novoseltsev wrote: > > Apparently our R interface does not, because it is started with > "--vanilla" switch, whose meaning is (on the bottom): > > --save Do save workspace at the end of the session > --no-save Don't save it > --no-environ Don't read the site and user environment files > --no-site-file Don't read the site-wide Rprofile > --no-init-file Don't read the user R profile > --restore Do restore previously saved objects at startup > --no-restore-data Don't restore previously saved objects > --no-restore-history Don't restore the R history file > --no-restore Don't restore anything > --vanilla Combine --no-save, --no-restore, --no-site-file, > --no-init-file and --no-environ > > Do we have any policy/reasoning for it? To me it seems sensible to allow > reading environment and configuration files so that users can customize > behaviour if they wish, and in general we should interfere with other > programs as little as possible. Took me a while to figure out why I cannot > set plotting options with config files... And it looks like there is no > other way but to patch Sage. > > Thank you, > Andrey > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
