aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/buffer.c
diff options
context:
space:
mode:
authorJustin M. Keyes <justinkz@gmail.com>2017-01-11 06:00:55 +0100
committerGitHub <noreply@github.com>2017-01-11 06:00:55 +0100
commit207ba359b0127fa5893b980abcb9186ffec1879c (patch)
treee055ede440eb3e06f2f9ba8db00f0ab16416369c /src/nvim/buffer.c
parenta08d2f54a0bd8cb9b6a4072a6adcc7eeee4690c2 (diff)
downloadrneovim-207ba359b0127fa5893b980abcb9186ffec1879c.tar.gz
rneovim-207ba359b0127fa5893b980abcb9186ffec1879c.tar.bz2
rneovim-207ba359b0127fa5893b980abcb9186ffec1879c.zip
Windows: vim_getenv(): Find runtime relative to nvim. #3303 (#5929)
In Windows we cannot rely on absolute install paths to point to the location of the runtime. Vim uses the path of the current binary as a possible location for the runtime folder. In Neovim the install location places the runtime folder in ../share/nvim/runtime. In Vim this logic is guarded by USE_EXE_NAME, which is defined for win32 and macOS. TODO: We may need to incorporate similar logic for macOS: https://github.com/vim/vim/blob/0cdb72aa38c4a0140c94d56bf8bc17cb30260ebf/src/misc1.c#L4287-L4308
Diffstat (limited to 'src/nvim/buffer.c')
0 files changed, 0 insertions, 0 deletions