-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Feature request: only reprocess modified files with --autoreload #2219
Comments
read the thread you linked.
we would need to track the influence of every input artefact (be it setting
or 'article'/'page' file) on all output files which are currently not doing.
if you feel up to the task of implementing go ahead and do it.
…On 3 October 2017 at 16:29, Greg Brener ***@***.***> wrote:
Pelican's --autoreload mode currently reprocesses every file, regardless
of how many were modified. Because many use this feature for interactive
editing - where usually only one file is modified at a time - a significant
speed boost could be gained if Pelican only reprocessed the modified files.
One potential approach for this is in #2171
<#2171>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2219>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEOv-oMrBzSnUBvb-EzDmwCfrEGGHrUGks5sokTLgaJpZM4PsNdS>
.
|
Sounds like someone was having a bad day. I hope things get easier for you. It turned out to be less time-consuming to port my site to Hugo, which already includes this feature. Feel free to re-open this issue if you think someone else will find it helpful. |
Hugo is great as a more general static site generator than pelican. However that particular feature is not supported by them afaik gohugoio/hugo#1643 or https://stackoverflow.com/questions/34714442/hugo-incremental-builds-is-there-an-undocumented-switch-somewhere (yet). |
Great to see that they take this issue seriously and are actively working on it. Hugo is so fast that I assumed that's what they were already doing. I was really asking for "fast interactive feedback while editing" which is what they provide, (surprisingly) without this feature. |
For anyone else finding this issue, check out Reading only modified content in the settings documentation. Enabling caching ( |
Pelican's
--autoreload
mode currently reprocesses every file, regardless of how many were modified. Because many use this feature for interactive editing - where usually only one file is modified at a time - a significant speed boost could be gained if Pelican only reprocessed the modified file(s). One potential approach for this is in #2171.The text was updated successfully, but these errors were encountered: