Occasionally, some part of your startup settings conflicts with a function call or package. You know this because things work when you use R --vanilla. Trying to find exactly where the conflict is. In such cases it would be useful to be able to quickly disable one or more startup files.
A poor mans version for this would be to have startup() as before processing each file, e.g.
One could also support a .startup.yml, which if found in a startup directory that is about to be processes, will be processed / acknowledged and be applied recursively.
Occasionally, some part of your startup settings conflicts with a function call or package. You know this because things work when you use
R --vanilla
. Trying to find exactly where the conflict is. In such cases it would be useful to be able to quickly disable one or more startup files.A poor mans version for this would be to have
startup()
as before processing each file, e.g.It should be possible to control this from the command line, e.g.
A fancier version would be to record the answers and save as a config file that can be reused and tweaked, e.g.
where
config.yml
may contain:One could also support a
.startup.yml
, which if found in a startup directory that is about to be processes, will be processed / acknowledged and be applied recursively.