Got it, thank you for pointing out the solution then.
Best,
Juan
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
I looks like you may have misunderstood my post so just to make sure:
There will be no patch to R to support this.
If this is something you want for yourself, then I have shown you how
you can do it. You can put the code in a startup file if you like.
If you want your students to have this, the
Thank you Mr. Tierney!
Using globalCallingHandlers() to directly handle
"packageConflictError" is an excellent idea!
The benefits I see for such an implementation are:
* The patch would be contained within the Conflict Error Handler,
which should reduce any side effects with an eventual implement
On Thu, May 21, 2020 at 10:37 AM wrote:
> Providing a way to more easily resolve situations that otherwise would
> be errors is a reasonable thing for an IDE to do.
In principle, yes.
However, I note that the word "easily" could mean different things to
different people.
Certain IDE* (not naming
Providing a way to more easily resolve situations that otherwise would
be errors is a reasonable thing for an IDE to do. I would prefer is
such things were optional and off by default, but other way not.
If an IDE does this and you don't approve then you don't have to use
it.
Best,
luke
On Wed
> An IDE could provide a more sophisticated interface, like a dialog
> allowing separate choices for each conflict. But this is best left up
> to the IDE or the user.
An IDE (or other user interface) should not alter the behavior of R,
especially the installing/loading/attaching of packages.
Ther
You can get what you are asking for now in R 4.0.0 with
globalCallingHandlers and using the packageConflictError object that
is signaled. This should get you started:
```
options(conflicts.policy = "strict")
packageConflictError
handle_conflicts <- function(e) {
cat(conditionMessage(e))
