-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Rebuild throttling #87
Comments
This project only builds when files are modified in the directories that it is "watching". If you modify Are you looking for more granular control over the delays in builds? If so, in what way do you envision it working? |
Yes I know what it does lol
Well we can start by exposing the delay option of Given this looks pretty relevant to what we are doing in sphinx-book-theme 😬
|
Ah. That's ez. :P |
This should be a +3/-3 code change, modifying our calls to server.watch(..., [with builder]) to have And, we'll want to update the documentation (README) to correctly note the new default as well as describe the new behavior. |
Narrator: it was not "ez"
Yea, so, it turns out, livereload does I'm borderline in the mood to start shipping livereload.js in this package instead of dealing w/ livereload. OTOH, I did spend all of sunday triaging 900+ notifications, so my brain is very mushy right now. >.< |
Uh well. I really don't like my free time: lepture/python-livereload#230 |
good lad! |
Duplicated by #174 |
It looks like
sphinx-autobuild
does have some rebuild throttling, i.e. it doesn't rebuild for every character you type.But I don't see any configuration currently for the time intervals involved?
It would also be interesting to consider configuration for turning off builds e.g. if the change is only adding new-lines/whitespace.
At the extreme, it would also be interesting if you could restrict rebuilds to only some kind of "trigger", like a key-board shortcut. No idea how that could work, but it would be cool.
What I am envisaging is packaging this as an extra in jupyter-book (with a
jb live
CLI command for firing up), for live book reloads.In this context, really frequent reloads would probably be unwelcome, especially if it also triggers a re-execution of a Jupyter Notebook!
(although this would also be limited by our jupyter-cache functionality, which only triggers re-execution on code changes, not text 😄)
Thoughts @pradyunsg?
(cc also @choldgraf)
The text was updated successfully, but these errors were encountered: