don't use package subdir within the project dir? about spades.project HOT 15 CLOSED

@eliotmcintire from comment in the issue linked above:

I had success setting files to ignore with the file_monitor_ignored_components setting in rstudio-prefs.json.

This seems to be working...I've added the following, but note this is user level setting, not project level.

    "file_monitor_ignored_components": [
        "data/",
        "inputs/",
        "packages/"
    ]

from spades.project.

I is not quite a user level setting, sadly. It is a user session level setting. So, it has to be reset for every project.

from spades.project.

Not true. If it's not sticking, you likely missed a comma or something in the prefs list. It's persisting across sessions for me.

from spades.project.

"session" means "project". So if you start a new project, you have to reset this. It must be in the project folder.

from spades.project.

No, it persists across sessions and projects. This is a user level setting. I’ll post screen shots showing how to set it.

from spades.project.

Go to ‘Help’ menu, under ‘Diagnostics’ is ‘Edit User Prefs File’.

from spades.project.

Alternatively, if you are on Linux, edit ~/.config/rstudio/rstudio-prefs.json directly.

from spades.project.

Either this does not work on Windows, or I am unable to follow instructions. Either way, this mechanism is either difficult or not viable as a means of a Windows machine to avoid monitoring every file in the packages folder. In a new project, please allow the packages folder to be outside the Rstudio project.

from spades.project.

I've confirmed it does work on Windows.

You can use another directory. Simply update it in .Rprofile, and possibly the top of 00-global.R.

But I will add an argument to allow passing a custom package directory.

from spades.project.

Why is it in .Rprofile? How did that get there?

from spades.project.

That's the mechanism to set the lib paths when the project is opened. It's the same mechanism as packrat/renv.

from spades.project.

Since I don't use those 2 packages (they have never worked when I tried them, plus they took a long time to set up), I cannot report whether Rstudio becomes unresponsive due to those packages. If those packages do make RStudio unresponsive, then lets not copy that! If they don't make RStudio unresponsive, then we have to figure out how they do it.

from spades.project.

per the links above: they have hardcoded exclusions in the Rstudio source code. But the prefs.json workaround does work.

from spades.project.

Since this is not a simple workaround (i.e., you have to understand json language a little bit, find a hidden folder, find an editor that works reliably -- the Rstudio one that opens when I follow the photo above is very buggy and doesn't show keystrokes on my machines, and make no syntax errors or else the changes are wiped with no error message) , I think it is very important that the default package location not be inside the package, unless there is way for the SpaDES.project to change the prefs.json file. I believe it is not sensible to create an unresponsive Rstudio environment by default.

from spades.project.

I agree that Rstudio's behaviour is obnoxious in this regard.

So what would be a good default location? <projectName>_packages/ in the project's parent directory?

I'll implement this to start and we can see how it goes.

from spades.project.