aemoncannon/ensime — pull request #311 by pashky (2013-04-11 09:12:37+00:00)
Title: Symlinks and index

Hi,

So, here's the situation: I'm working out of some obscure long path directory, which is symlinked into other more convenient for me location. I never use real path myself, yet ensime seems to expand symlinks when it builds the index. Then file name comparisons fail, and compilation error navigation no longer works.

This change did fix M-n/M-p for me, and didn't break anything else so far, which is nice. Yet the other problem is that when I start navigating across the files, those coming from index open under real long path. So I get a mix of buffers with two different path prefixes, buffer list becomes a real mess, mark by file name mask fails etc.

I feel like server probably shouldn't be normalizing paths in the first place. What is your opinion on that? Was it deliberate?