-
-
Notifications
You must be signed in to change notification settings - Fork 39
On watch, every single file calls out to Git #24
Comments
You can keep a hash if you want on the Determinator maybe? |
I understood maybe five of those words. So a Hash is kept, and then what? "Rerun Determinator if |
@gjtorikian Sure, or just keep an ongoing cache of all the dates (unformatted of course) and don't rebuild anything in the current process. That would ensure, when using That hardly makes sense to me in words. Sorry I suck at words today. |
❤️ |
I think the sexy rewrite nullified this. I can no longer reproduce the error. |
YAYYYY 🎉 sexy = perf |
Still an issue. |
Are you using |
The latter, though maybe I should switch to the former? Either way the problem needed to be fixed. |
Definitely use |
How do I install this as a plugin within jekyll ... I created a _plugin directory and git cloned into it now what ? |
@AnandLA @parkr @gjtorikian I can only use
If I try to include How to fix this please? |
I'm experiencing a similar issue to @888ba8.
If I remove Anyone figure out a way to add "Last updated" to a Jekyll blog? I tried a few other solutions, but none seem to work. |
{% page.last-modified-at %} Liquid Exception: Liquid syntax error (line 49): Unknown tag 'page' in README.md
Pre-0.3.0, Jekyll sites would crash with this plugin and
--watch
. Now, they remain, but generation takes a really long time, because every single file needs a Git call to check the time.@parkr Is there a way to run a plugin once, before the server starts up, and not every time an auto-regeneration occurs? If not, the only thing I can think of is to preserve some kind of hash, like
@matches[absolute_path_to_article] = last_change
, and just not even attempt the last_modified_at check if the file was checked once before.The text was updated successfully, but these errors were encountered: