Symlinks pointing to directories inside a projectile project are added to projectile files cache

[colonelpanic8]

Sorry for the obscure/confusing title. I'm finding it difficult to accurately articulate exactly what the issue is in an abstract way, so let me provide an example to clarify:

I have a source controlled dotfiles project that lives in ~/dotfiles. Everything inside of ~/dotfiles/dotfiles, including, for example, ~/dotfiles/dotfiles/emacs.d, is pointed at by a symlink in ~ with an identical name (though prefixed with a dot). If a file is opened through the symlinked path, projectile correctly recognizes that the file is part of the ~/dotfiles project, but it then adds the relative path of the file through the symlink (rather than inside of the project) to the project's filepath cache. This means that the file cache gets populated with things like

../.emacs.d/elpa/projectile-20150223.8/projectile.el

Now that I am investigating a bit more, it seems that this only happens with files that are ignored by projectile in the actual directory. It seems that what might be happening is that projectile is not recognizing that the relative filepath ultimately links to a path that is ignored. It might be difficult to come up with a proper resoultion to this issue since you might not always WANT to ignore symlinks that link to other ignored files. However, I would make the argument that any filepath that is outside of the main project should never be added to the projectile file cache.

Sorry if any of this is confusing; let me know if there is anything that needs elucidation.

[colonelpanic8]

This actually seems to happen even with files that are not ignored. I'm not sure why I thought it only happens with files that ignored.

@bbatsov Do you have an opinion about what should be happening here?