Perhaps my example was too simplistic; the point isn't that I expect the plugin 
to be looking for the compile-time include directories, it's that there are 
some cases where the current behavior is 99% guaranteed to be wrong. If I am 
working on some project in a directory such as $HOME/src/project1 then an 
already-open header from $HOME/src/project2/tree/directory should not match if 
there is a header in the project1 directory which can be matched.

The point is that the plugin doesn't even check the current file's directory 
before switching to an already-open file, leading to behavior where switching 
to the header will switch to the wrong head, and then trying to switch back 
will switch to a different file than the user was originally viewing.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Reply via email to