-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lintr session does not load init file #40
Comments
@adamaltmejd Thank you for your good idea! |
Hi! Thanks! I would let r.term.option default to Thanks for your great work, almost wanting to drop iTerm for this extension :). |
@adamaltmejd Thank you and sorry my late reply. |
Excellent, thanks! |
Hey,
I have a ~/.Rprofile file that among other things contains
.libPaths("~/.R/packages")
. Saving all packages in a user-defined library. This is useful for many reasons, and most things in vscode-R work well as long as I change the main startup settings to not include "vanilla":"r.rterm.option": ["--no-save"]
But it seems that the R session that lints code is still loaded using the
vanilla
option since vscode-R keeps nagging me about the linter not being installed each time I save an .R file, even if the lintr library is loaded in the console. Trying to install things in the default directory doesn't work properly when R is installed with Homebrew (probably due to this issue: Homebrew/homebrew-core#17098). But even if it would, the "install lintr" command executes install.packages("lintr") to my own library so after a successful install, it still cannot find the package.According to
man R
:Why do you need to run --no-site-file, --no-init-file and --no-environ? My suggestion would be to default to only --no-save and --no-restore, for both the lintr session and the console session.
The text was updated successfully, but these errors were encountered: