To clarify, I am going to fix the issue in the methods package
(actually I already have but need to test further). There's no intent
to change the behavior of q().
On Thu, Apr 19, 2018 at 8:39 AM, William Dunlap wrote:
> The problem is not specific to redefining the q function, but to
> the inter
The problem is not specific to redefining the q function, but to
the interaction of assignInNamespace and setGeneric. The
latter requires, roughtly, that the environment of the function
being replaced by an S4 generic is (or is the descendent of)
the environment in which it lives.
E.g., the follo
> Michael Lawrence
> on Wed, 18 Apr 2018 14:16:37 -0700 writes:
> Hi Bill,
> Ideally, your coworker would just make an alias (or shortcut or
> whatever) for R that passed --no-save to R. I'll try to look into this
> though.
> Michael
Yes, indeed!
As some of you
Hi Bill,
Ideally, your coworker would just make an alias (or shortcut or
whatever) for R that passed --no-save to R. I'll try to look into this
though.
Michael
On Wed, Apr 18, 2018 at 1:38 PM, William Dunlap via R-devel
wrote:
> A coworker got tired of having to type 'yes' or 'no' after quittin
A coworker got tired of having to type 'yes' or 'no' after quitting R: he
never wanted to save the R workspace when quitting. So he added
assignInNamespace lines to his .Rprofile file to replace base::q with
one that, by default, called the original with save="no"..
utils::assignInNamespace(".q
