-
Notifications
You must be signed in to change notification settings - Fork 14
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
M-x quarto-preview
does not refresh
#5
Comments
M-x quarto-preview
does not refresh
This is by design, in order to match the behavior of other markdown emacs modes. Nevertheless, when If you want to propose a PR that adds the ability to customize this behavior, I'd be happy to look it over. It'd have to add a customization variable that controls the creation of the command parameter in With that said, I won't have time to do this until at least mid-August. |
Perhaps mention this in the main site? According to the current description, "Start a quarto preview server that watches quarto content for changes and automatically refreshes it". |
Good catch, that's stale documentation. |
For me that's |
EDIT Haha, just noticed this was already mentioned in the original issue. Anyway, might be handy to leave this message here... END EDIT I would say a better workaround is to start the But I do not understand this design decision. Why does it have to match the behavior of other markdown modes (b.t.w. also it does not match the behavior of markdown-soma? Quarto looks otherwise great b.t.w.! Thanks for this nice software... |
I agree that this behavior should at least be easily customizable. And, of course, I agree with the praise. :) |
@henningninneh emacs is no longer my day-to-day editor and we have a ton of other things to work on, so unfortunately this is relatively low-priority right now. But we appreciate pull requests! |
Running
M-x quarto-preview
on a.qmd
file previews as expected, but does not refresh when the document is changed and saved. The expected behaviour can be seen when runningquarto preview file.qmd
in a shell.The text was updated successfully, but these errors were encountered: