Skip to content
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

[FR] Suggest to readRenviron() after edit_r_environ() instead of restarting R #1890

Closed
ColinFay opened this issue Aug 31, 2023 · 3 comments
Closed
Labels
edit 🧞‍♂️ feature a feature request or enhancement

Comments

@ColinFay
Copy link

Running edit_r_environ() returns the following message:

> usethis::edit_r_environ()
• Modify '/Users/colinfay/.Renviron'Restart R for changes to take effect

The message suggests that the user should restart R, but there is also the readRenviron() function, which is design to, well, read the .Renviron file.

I wonder if the message of edit_r_environ() could be

> usethis::edit_r_environ()
• Modify '/Users/colinfay/.Renviron'Restart R for changes to take effectYou can also source the file with readRenviron('/Users/colinfay/.Renviron')

Happy to draft a PR

Colin

@hadley
Copy link
Member

hadley commented Nov 3, 2023

If we could this we should also recommend source() after edit_r_profile(). And in both case, need to make sure that the code link is clickable.

A PR would definitely be appreciated 😄

@hadley hadley added feature a feature request or enhancement edit 🧞‍♂️ labels Nov 3, 2023
@jennybc
Copy link
Member

jennybc commented Nov 3, 2023

I think it's always a good idea to encourage people to restart R 😄

@jennybc
Copy link
Member

jennybc commented Jul 22, 2024

I'm sticking by the advice that the best move after editing these startup files is to restart R.

@jennybc jennybc closed this as not planned Won't fix, can't repro, duplicate, stale Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
edit 🧞‍♂️ feature a feature request or enhancement
Projects
None yet
Development

No branches or pull requests

3 participants