diff options
author | Yegappan Lakshmanan <yegappan@yahoo.com> | 2024-04-20 18:31:21 +0200 |
---|---|---|
committer | Christian Brabandt <cb@256bit.org> | 2024-04-20 18:31:21 +0200 |
commit | f135fa28e481b2eba73baf52b08d24add5c4fe8b (patch) | |
tree | 646542a459b5b3876845570b7a7c77c7a18783ea /pixmaps/tb_undo.xpm | |
parent | 8927c9b720135610a1193999d29be76927b05ab3 (diff) |
patch 9.1.0359: MS-Windows: relative import in a script sourced from a buffer doesn't workv9.1.0359
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 #14588
closes: #14603
Signed-off-by: Yegappan Lakshmanan <yegappan@yahoo.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'pixmaps/tb_undo.xpm')
0 files changed, 0 insertions, 0 deletions