diff options
| author | Jan Edmund Lazo <jan.lazo@mail.utoronto.ca> | 2025-10-20 21:20:08 -0400 |
|---|---|---|
| committer | Jan Edmund Lazo <jan.lazo@mail.utoronto.ca> | 2025-10-20 22:21:09 -0400 |
| commit | 2a28149efc705ca5f2e53a8f3ed08912afa885eb (patch) | |
| tree | 54cab46c8fe241d49697e70100982a9ad1bc58f7 /runtime/lua/vim | |
| parent | 96a514ed464d5583bebd2d3631cbcb8cd71b45e3 (diff) | |
| download | rneovim-2a28149efc705ca5f2e53a8f3ed08912afa885eb.tar.gz rneovim-2a28149efc705ca5f2e53a8f3ed08912afa885eb.tar.bz2 rneovim-2a28149efc705ca5f2e53a8f3ed08912afa885eb.zip | |
vim-patch:9.1.0359: MS-Windows: relative import in a script sourced from a buffer doesn't work
Problem: MS-Windows: Relative import in a script sourced from a buffer
doesn't work (Ernie Rael)
Solution: Set a filename, so that we are not trying to use
script-relative filename (Yegappan Lakshmanan)
When a script is sourced from a buffer, the file name is set to ":source
buffer=". In MS-Windows, the ":" is a path separator character (used
after a drive letter). This results in the code trying to use the ":"
prefix to import the script on MS-Windows. To fix this, when importing a
script from a script sourced from a buffer with nofile, don't use
a script relative path name.
fixes vim/vim#14588
closes: vim/vim#14603
https://github.com/vim/vim/commit/f135fa28e481b2eba73baf52b08d24add5c4fe8b
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
Diffstat (limited to 'runtime/lua/vim')
0 files changed, 0 insertions, 0 deletions