Use relative path when possible

[eric-hansen]

Introduces a new variable: vim_tree_load_git_file_relatively to not impact previous behavior. If non-nil then will attempt to use the absolute path, assuming within a Git project. I couldn't find a way to do it otherwise and didn't want to spend too much time hacking this about.

Resolves #482

[smartding]

please don't assume we're always within a git project, I use nvim to edit non-git-managed files too

[eric-hansen]

please don't assume we're always within a git project, I use nvim to edit non-git-managed files too

Fixed. :)

[sindrets]

This won't work when the git root is not the cwd of the tree. Also, this will be enabled even when:

let g:nvim_tree_load_git_file_relatively = 0

Which goes against how we treat all the other boolean options. #487 is a better approach.

[eric-hansen]

Gotcha. Since you believe #487 is the better approach I've went and closed this out.

[Hubro]

For some reason this change was reverted:

099f905

And nvim-tree is once again opening all files using an absolute path, which is a huge pain for me.

Why was the change reverted? Is there something we can do to re-introduce it?

---

EDIT: Right, seems like it caused this bug: #495

Anything that can be done to fix it?

[smartding]

@Hubro
I don't seem to experience the bug described in that video in #495, so I just kept my patch in my own fork, the patch only changes two lines of code.

[fragov]

Same issue. Btw, Telescope opens files with relative paths.
Can this be fixed?

[alex-courtis]

Same issue. Btw, Telescope opens files with relative paths. Can this be fixed?

There is little consistency between plugins and whether they open files relatively or absolutely.

It should be possible to open relatively; please raise a feature request.