{"action":"created","issue":{"url":"https://api.github.com/repos/guard/listen/issues/363","repository_url":"https://api.github.com/repos/guard/listen","labels_url":"https://api.github.com/repos/guard/listen/issues/363/labels{/name}","comments_url":"https://api.github.com/repos/guard/listen/issues/363/comments","events_url":"https://api.github.com/repos/guard/listen/issues/363/events","html_url":"https://github.com/guard/listen/issues/363","id":126770654,"number":363,"title":"Shouldn't ignore prevent symlink errors?","user":{"login":"lisad","id":484337,"avatar_url":"https://avatars.githubusercontent.com/u/484337?v=3","gravatar_id":"","url":"https://api.github.com/users/lisad","html_url":"https://github.com/lisad","followers_url":"https://api.github.com/users/lisad/followers","following_url":"https://api.github.com/users/lisad/following{/other_user}","gists_url":"https://api.github.com/users/lisad/gists{/gist_id}","starred_url":"https://api.github.com/users/lisad/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lisad/subscriptions","organizations_url":"https://api.github.com/users/lisad/orgs","repos_url":"https://api.github.com/users/lisad/repos","events_url":"https://api.github.com/users/lisad/events{/privacy}","received_events_url":"https://api.github.com/users/lisad/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-01-14T23:16:05Z","updated_at":"2016-04-27T13:57:51Z","closed_at":"2016-04-27T13:57:51Z","body":"I've read the helpful documentation about how symlinks cause warnings about \"directory already being watched\".  This is noise in my guard reporting, so I investigated how to avoid the warnings.  Having considered all the options, I think symlinks are pretty useful in projects (e.g. we avoid duplicating assets in our directory by symlinking those assets between the modules that need those assets, so if we change our logo it changes on the Web and in the client).\r\n\r\nThe 'ignore' feature seemed perfect, except for the clear documentation that it doesn't work, because \"events are only filtered after they are fired\".  Why wouldn't it be considered a useful feature in 'ignore' for 'ignore' to act at an earlier level?  Or that 'ignore' would filter this duplicate directory warning as well as filtering events after they are fired?  "},"comment":{"url":"https://api.github.com/repos/guard/listen/issues/comments/215091793","html_url":"https://github.com/guard/listen/issues/363#issuecomment-215091793","issue_url":"https://api.github.com/repos/guard/listen/issues/363","id":215091793,"user":{"login":"e2","id":150197,"avatar_url":"https://avatars.githubusercontent.com/u/150197?v=3","gravatar_id":"","url":"https://api.github.com/users/e2","html_url":"https://github.com/e2","followers_url":"https://api.github.com/users/e2/followers","following_url":"https://api.github.com/users/e2/following{/other_user}","gists_url":"https://api.github.com/users/e2/gists{/gist_id}","starred_url":"https://api.github.com/users/e2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/e2/subscriptions","organizations_url":"https://api.github.com/users/e2/orgs","repos_url":"https://api.github.com/users/e2/repos","events_url":"https://api.github.com/users/e2/events{/privacy}","received_events_url":"https://api.github.com/users/e2/received_events","type":"User","site_admin":false},"created_at":"2016-04-27T13:57:51Z","updated_at":"2016-04-27T13:57:51Z","body":"I'm planning to solve this with: https://github.com/guard/listen/issues/381\r\n\r\nBasically, once Listen has an internal database of symlinks, you should be able to watch symlinks properly."}}