-
Notifications
You must be signed in to change notification settings - Fork 92
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
R: loose ends in the vignette workflow #1471
Comments
Related to or maybe just part of #1421 |
I have accidentally hit "Preview" on a NEWS file in Positron and it made just a ton of files I had to manually clean up afterward. In RStudio, looks like "Preview" makes the HTML in my temp directory, which I much prefer: The "Preview" button in Positron comes from the Quarto extension, right? What are some options for changing what this does? |
Everything described here continues to happen (file explosion and terminal occupied with file watching). |
Similarly problem with hugodown blog posts, with the additional problem that quarto generates a |
This came up in private beta here (specifically about README preview going to the working directory): https://github.com/posit-dev/positron-beta/discussions/130 |
Started work on this in quarto-dev/quarto#435 |
Let me update where we are on this: Quarto uses the terminalQuarto using a terminal to serve a preview is as designed and we don't have a straightforward way to run it somewhere secretly in the background. It is quite straightforward to open a new terminal so I don't think this is a big usability problem (instead, a difference for folks to get used to): Quarto puts a bunch of files where it rendersWe are in the process of fixing where the contents of "Quarto: Preview" go when you are in an R package, in quarto-dev/quarto#435 plus some work that @cscheid is doing in Quarto itself. The outcome here will be that the HTML and other files will go to a temp directory and will not show up in the R package directory. What about hugodown?For hugodown @hadley, the big challenge is
To instead say:
Alternatively, you can update the package to use Quarto explicitly, with |
Just to add a bit more wrt We expect that these helper functions would catch a large fraction of common use cases, so that specific pain point would be alleviated substantially. |
Just for clarity, this particular |
To be clear, all I want for hugodown is for |
@hadley I might be missing something, but does |
@cscheid yeah, I mean run |
I'm going to add detail to #1421 to explore options for that @hadley. Let's make this issue "R package development For QA and confirming that we have the behavior as expected now, one will need to:
Then you will be set up to check behavior: In an R package workspace
In a workspace that is not an R package
|
Current versions of Positron and quarto and the quarto extension: Positron Version: 2024.05.0 (Universal) build 1283
✅ In an R package, if I click the "Preview" button, an html preview of the NEWS file appears in the Viewer and no related files are left behind in the source package. Ditto for a vignette. (The change made to ✅ In a folder that is not an R package, if I click the "Preview" button for an |
I've just enjoyed the new runtime support for
.Rmd
files (#1043), in the context of working on package vignettes.One thing I did was to click "Preview" and I notice a few things about the state that leaves Positron in:
vignettes/VIGNETTE-TITLE_files/
. I suppose this could just be something to resolve with gitignore. But it feels like RStudio must take my stuff to some more behind-the-scenes location before render?The text was updated successfully, but these errors were encountered: