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

Ignore specific files and directories #222

Open
Tcll opened this issue May 23, 2015 · 5 comments
Open

Ignore specific files and directories #222

Tcll opened this issue May 23, 2015 · 5 comments

Comments

@Tcll
Copy link

Tcll commented May 23, 2015

I'm not sure if this is not implemented, or just not documented, but either way, I'm having some major difficulties trying to ignore a few large runtime directories...

everything I've tried to specify the directories doesn't work...
they keep reappearing whenever I remove some extra data files created during runtime...

how can I tell floobits to ignore these directories??

@ggreer
Copy link
Member

ggreer commented May 24, 2015

Have you tried adding the files or directories to a .flooignore file? It should work just like .gitignore, .hgignore, etc.

@Tcll
Copy link
Author

Tcll commented May 24, 2015

ok that's what I originally thought...

but, no matter what I did to the flooignore file, every time I removed my test directory and put something in it, it kept reappearing on the web IDE :/

or do changes to flooignore take effect next time you join the workspace??

@ggreer
Copy link
Member

ggreer commented May 25, 2015

Changes to .flooignore only take effect when joining the workspace. I wish it were otherwise, but there's no cross-platform API for noticing when a file changes. select() comes close, but on Windows it only works on sockets.

@Tcll
Copy link
Author

Tcll commented May 25, 2015

ah alright thanks, perhaps that little watchdog extension I posted about in the other issue might help. :)

@arxpoetica
Copy link

Where is the watchdog extension? .flooignore isn't very helpful without a watch. 😫

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