Been there also. _My_ solution was not to rely anymore on stuff provided by a heavyweight IDE. "Jumping to somewhere in an unbuffered file according to where I

Been there also. _My_ solution was not to rely anymore on stuff provided by a heavyweight IDE. "Jumping to somewhere in an unbuffered file according to where I am in the current buffer", that is actually depending on a background worker that knows a very specific set of rules and use it to constantly cycle threw the filesystem. Which bg process is usually provided by tanks like Eclipse. With the time I've found something that matches that behavior without the payload on the computer, and guess what, it's my brain. I'm no more in pain of jumping to the definition of a css rule, because I know which css file I have to invoke and I can do it _very_ quickly thanks to Control+P, and jumping to the definition is a matter of one or two "/". Of course you need to organize things smartly in your project if you ever want to do that without too much thinking time, but hell, I count that on the bright side of this solution.