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

ignores new directoried #3

Closed
GReagle opened this issue Jan 7, 2016 · 5 comments
Closed

ignores new directoried #3

GReagle opened this issue Jan 7, 2016 · 5 comments

Comments

@GReagle
Copy link

GReagle commented Jan 7, 2016

entr, while in -d mode, doesn't exit when a new subdirectory is created or when the new subdirectory gets a new file.

By the way, great program. Thanks.

@jwerle
Copy link
Member

jwerle commented Jan 7, 2016

@GReagle Please report issues to the original project repo here
cc @eradman

@jwerle jwerle closed this as completed Jan 7, 2016
@eradman
Copy link
Contributor

eradman commented Jan 7, 2016

Specifically you are encountering this issue:
https://bitbucket.org/eradman/entr/issues/27/not-working-on-a-vagrant-box-when-local

@GReagle
Copy link
Author

GReagle commented Jan 8, 2016

@jwerle Thank you for the link to the original project repo.
@eradman I have no idea why you refer to issue 27. My issue has nothing to do with a "Vagrant Box" (whatever that is), or NFS, or ssh, or any networking.

Anyway, I'll clone from the bitbucket original project repo and re-build and re-test. If the problem still occurs I'll open an issue on bitbucket.

@jwerle
Copy link
Member

jwerle commented Jan 8, 2016

FYI - I've updated this repo with the latest release from Eric.

On Thu, Jan 7, 2016, 7:02 PM GReagle [email protected] wrote:

@jwerle https://github.com/jwerle Thank you for the link to the
original project repo.
@eradman https://github.com/eradman I have no idea why you refer to
issue 27. My issue has nothing to do with a "Vagrant Box" (whatever that
is), or NFS, or ssh, or any networking.

Anyway, I'll clone from the bitbucket original project repo and re-build
and re-test. If the problem still occurs I'll open an issue on bitbucket.


Reply to this email directly or view it on GitHub
#3 (comment).

@eradman
Copy link
Contributor

eradman commented Jan 8, 2016

@GReagle right, sorry I rashly assumed you were hitting yet anther instance of an inotify blind spot using stack mount points

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

No branches or pull requests

3 participants