Skip to content
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

Jekyll keeps regenerating when output folder already exists. #340

Closed
manuelmeurer opened this issue Jun 2, 2011 · 10 comments
Closed

Jekyll keeps regenerating when output folder already exists. #340

manuelmeurer opened this issue Jun 2, 2011 · 10 comments

Comments

@manuelmeurer
Copy link

When I start Jekyll using jekyll --auto and the output folder (public in my case) already exists, it keeps regenerating some files:

18:01:33 (ruby-1.9.2-p180@rails3) ~/apps/app jekyll --auto
Configuration from /Users/me/apps/app/_config.yml
Auto-regenerating enabled: /Users/me/apps/app -> ./public
[2011-06-02 18:01:37] regeneration: 43 files changed
[2011-06-02 18:01:38] regeneration: 14 files changed
[2011-06-02 18:01:39] regeneration: 5 files changed
[2011-06-02 18:01:40] regeneration: 5 files changed
[2011-06-02 18:01:41] regeneration: 5 files changed
[2011-06-02 18:01:42] regeneration: 5 files changed
[goes on indefinitely]

When I remove the public folder and restart Jekyll, it works fine:

18:01:43 (ruby-1.9.2-p180@rails3) ~/apps/app rm -rf public/
18:01:45 (ruby-1.9.2-p180@rails3) ~/apps/app jekyll --auto
Configuration from /Users/me/apps/app/_config.yml
Auto-regenerating enabled: /Users/me/apps/app -> ./public
[2011-06-02 18:01:48] regeneration: 29 files changed

Using Jekyll 0.10.0

@amateurhuman
Copy link

I can confirm this behavior.

It appears to be a problem with directory_watcher, there is currently an open issue (#8) on that repo suggesting adding an ignore glob option that TwP is supporting.

@kbl
Copy link

kbl commented Dec 14, 2011

As soon as my pull request solving issue TwP/directory_watcher#8 will be approved I'll try to fix this behaviour.

@paulmsmith
Copy link

Any news on this? I'm getting the same using Jekyll 0.11.2

@paulmsmith
Copy link

Ah didn't catch the part about removing the output folder before running Jekyll auto. Did that and it solves it but obviously nice to have it fixed.

@hpyhacking
Copy link

I have same problem, public folder to use Pow, exclude option should apply to --auto option.

@hpyhacking
Copy link

Now, I don't put public to project root folder.

destination: /tmp/project/public

Now --auto works fine, ref /tmp/project to ~/.pow and LiveReload to watch /tmp/project.

Fixed, but not pretty.

@kevinSuttle
Copy link

I've had this same behavior with _public too.

@parkr
Copy link
Member

parkr commented Mar 17, 2013

Fix in #862.

@parkr parkr closed this as completed Mar 17, 2013
@arekstryjski
Copy link

I don't know why it is closed. I get this problem on one of my computers. Strangely not on the second one, but no idea what makes the difference... both are Linux Ubuntu.
The bug is definitely still there!

@codygman
Copy link

I'm getting this issue on debian wheezy. Jekyll just keeps regenerating endlessly

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants