Phil Runninger 52151fb307 Call Resolve on the file's path when calling :NERDTreeFind. (#896) ... When :NERDTreeFind creates a tree, it resolves the file's path, and makes that its root. See :h resolve() for more info; it basically tracks down links to their ultimate source. Then :NERDTreeFind tries to find the file under that root, so it can be revealed. The problem is that it compares the file's unresolved path against the resolved path in the root. Here is the scenario: /tmp/ is a link to /private/tmp/ :e /tmp/foo will open the file as expected :NERDTreeFind will first create a tree with a root of /private/tmp/ Then it tries to find /tmp/foo, but it can't, because the path names don't match. This commit resolves /tmp/foo to the actual location of /private/tmp/foo; thus, it is able to find the file in the tree.		2018-10-24 22:13:42 -04:00
..
nerdtree	Call Resolve on the file's path when calling :NERDTreeFind. (#896)	2018-10-24 22:13:42 -04:00
nerdtree.vim	Correctly check the type of the sort key's value. Fixes #842.	2018-07-01 19:55:26 -04:00