-
Notifications
You must be signed in to change notification settings - Fork 331
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
Recommended way to serve the site? #543
Comments
I think this is a RStudio IDE thing. The addin function is defined here: blogdown/inst/rstudio/addins.dcf Lines 1 to 4 in 2b1449d
and as you see, we just give the function name. I think RStudio IDE assumes this function to run addin may not be exported so it uses |
The answer is you only call
|
Ah gotcha, thank you so much- that helps! I'm working on learning resources and wanted to make sure I understood. Feel free to close :) @cderv do you think the |
We can close this issue after rstudio/rstudioapi#213 is fixed. I think |
Yes I think so. I'll open an issue in the IDE about that. |
Instead of waiting for the RStudio bug to be fixed, I just figured out another way to fix this problem. You should no longer see |
Clever solution! That is awesome! 👍 |
I typically use the Add-in to serve the site, and I just noticed that
serve_site()
appears to be an exported function.Yet, when I use the Add-in, this prints to my console:
But then sometimes when I'm editing a blog post, this prints to my console:
Reading the actual function definition here, I see why they are different. But I was confused. I think we want to encourage
serve_site()
to start? If so, I cannot see where to change where those:::
print to the console.The text was updated successfully, but these errors were encountered: