Allow passing R arguments to rig run #249
Description
Activity
AFAICT it never saves the data, so you don't need
--no-save. Which arguments would you like to use in particular?I do get the
Save workspace image? [y/n/c]:prompt when quitting with Ctrl-D (or the signal sent by iron.nvim) and as well with justq().I can make an alias
q <- function(save="no", ...) quit(save = save, ...)
in my .Rprofile but that does not change the behavior on Ctrl-D
Specifying
--no-savedoes make a difference:$ rig run […] > q() Save workspace image? [y/n/c]: ^D$ R --no-save […] > q() [quits without prompt]weirdly not in my case
I > R --no-save [..] > q() Save workspace image? [y/n/c]: nlet me check on another computer
ok apparently that has to do with an alias malfunctioning on my end.
Very sorry for thatOh, right, so you are running it without any arguments? Then it would indeed make sense to be able to pass some arguments....
Yes, I guess having a way to pass argument into
rig runto the sub call (R, RScript, etc) could be useful.I suggested
rig run -- --no-saveas it reminds me ofcargo run a_project -- arguments_to_the_projectA modest proposal: make
rig runan alias forR --no-save --no-restoreinstead of currently justR, to shed some historical ballast (the default R settings of saving/restoring globalenv is daft).Reacted by Adrien Le Guillou@klmr Yeah, I like that.
I wouldn't mind having either
--vanillaor--no-init-fileand--no-site-file. I find it useful when working in a renv project, but wanting do something outside the limited library (e.g. check docs of a package I have installed globally).- added a commit that references this issue
on Sep 25, 2026 This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue
- locked as resolved and limited conversation to collaborators
on Oct 1, 2026
Hi,
is there a way to pass
Rarguments like--no-savetorig run?something like
rig run -- --no-saveThanks