Hi Jose and Ari,
Many good points were raised by Ari. I'd simply add an observation of mine, that I made a couple of days ago, after updating Tinn-R.
[Main topics of my comments: Package installation; Confusion between library paths]
My computer has admin rights, so R is allowed to install packages into Program Files if I tell "him" to do so. And that's usually what I want, because I prefer to keep My Documents folder free from non-"document" files... mostly to make backups of this folder lighter. Ok, so... Just after Tinn-R program was updated, when I started it, I had this issue of "infinite loop of trying to install TinnRcom pkg". It seemed Tinn-R was not satisfied by any install iteration, telling me that the "installed" version was not up-to-date. And when I took a look at the contents of R library folder, I saw that it had "TinnRcom", "formatR", "svSocket" and "svMisc" folders. That would be okay... IF Tinn-R did not wish to install its required packages into another path, of the form "C:/Users/{USER}/Documents/R/win-library/3.3". Hence, my hypothesis is that this "infinite" loop occurs when there are duplicated versions of those required-by-TinnR packages, due to the fact than there are two possible library paths.
By the way, I don't know if other Tinn-R users wish the same, but I would like to be able to force Tinn-R to use one library path for ALL package installs, including the ones that "he" tries to install/update right after Tinn-R program install/update (i.e. "TinnRcom", "formatR", "svSocket" and "svMisc"). I've noticed that even if I change the "Default to install and update packages" to ".libPaths()[2L]" for targeting Program Files/... path, it ignores this when trying to install TinnRcom et al. Because of this, I cannot prevent Tinn-R from creating these 4 folders in My Documents, which I dislike.
But maybe I lack a piece of information? Is there a way to permanently modify these path strings, in some INI text file for example? That could be sufficient.
Besides, would it be possible to tell R to use the same install path target as Tinn-R, at least when R (R console) is launched by Tinn-R?
(because at present, if I use the Install button within Tinn-R, it takes my ".libPaths()[2L]" custom setting into account, BUT if I install a package directly from R console menus, it ignores my custom setting and therefore uses .libPaths()[1L].
And very last suggestion: I know that I should send my request directly to the R development team, but since you're closer to R IDE development than I, I prefer to share my idea with you, Jose. The window that pops up for installing packages in R is very simple, and that's ok. But we all know that there are thousands of available packages, so... Why isn't there a way to find the right package faster? I dislike having to use my mouse to scroll up and down 'til I locate the right starting letter, then the full name of the package I want. In almost every long list similar to this one, it is possible to type the first couple of letters of the searched name. If you find this is a good idea, Jose, would you accept to send this R-GUI simple feature request to the appropriate branch of R development team? That would be a subtle but nonetheless very appreciated improvement of that "Packages " window.
That completes what I wanted to add to Ari's post.
Thanks for reading!
And nice weekend to you.
Marc.