Returning to the previous location can fail if the previous file is
in a different directory to the current one, because only the file's
basename is stored in the location stack.
This patch fixes this by storing the fully qualified path in the stack.
E.g. after opening dirA/foo, then jumping to dirB/bar, trying to go back would make vim try and open dirB/foo, when it should be dirA/foo.
Hi,
Returning to the previous location can fail if the previous file is in a different directory to the current one, because only the file's basename is stored in the location stack.
This patch fixes this by storing the fully qualified path in the stack.
E.g. after opening dirA/foo, then jumping to dirB/bar, trying to go back would make vim try and open dirB/foo, when it should be dirA/foo.
Cheers!