Getting Access To Original File Path (Un-standardized)

[joefitzgerald]

I see that in 2013, you ran into many issues with symlinked paths (#320, #329). I would like to get access to the file path for the project root and files / directories within that are not standardized so that I can use the non-standardized paths with external tools.

See joefitzgerald/go-plus#50 for additional context.

This commit seems to have introduced standardized paths: 82bce08

[joefitzgerald]

Said another way: if a user opens a file that happens to reside somewhere underneath a symlinked folder, I'd like to be able to use the symlinked path rather than resolving the symlink to its actual destination.

As there is no way for me to go in reverse, the lack of this feature essentially renders symlinks incompatible for scenarios where residing underneath a specific path is required (e.g. in go, your source must reside underneath $GOPATH/src; some people symlink directories underneath this back out to ~/projects/mylibrary or similar).

[rtorino]

I encountered the same issue. My .lintrc files in my project root are not read since those are just symbolic path from a git submodule directory.

[joefitzgerald]

Closing in deference to #9879.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!