Mercurial > vim

comparison runtime/doc/builtin.txt @ 28672:e4de5b5193b4 v8.2.4860

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.4860: MS-Windows: always uses current directory for executables Commit: https://github.com/vim/vim/commit/05cf63e9bdca1ac070df3e7d9c6dfc45e68ac916 Author: Yasuhiro Matsumoto <mattn.jp@gmail.com> Date: Tue May 3 11:02:28 2022 +0100 patch 8.2.4860: MS-Windows: always uses current directory for executables Problem: MS-Windows: always uses current directory for executables. Solution: Check the NoDefaultCurrentDirectoryInExePath environment variable. (Yasuhiro Matsumoto, closes #10341)
author Bram Moolenaar <Bram@vim.org>
date Tue, 03 May 2022 12:15:04 +0200
parents 5ef46b938c6e
children 38f7a132bba3
comparison
equal deleted inserted replaced
28671:5865b00cca76 28672:e4de5b5193b4
2014 without an extension. When 'shell' looks like a Unix shell, 2014 without an extension. When 'shell' looks like a Unix shell,
2015 then the name is also tried without adding an extension. 2015 then the name is also tried without adding an extension.
2016 On MS-Windows it only checks if the file exists and is not a 2016 On MS-Windows it only checks if the file exists and is not a
2017 directory, not if it's really executable. 2017 directory, not if it's really executable.
2018 On MS-Windows an executable in the same directory as Vim is 2018 On MS-Windows an executable in the same directory as Vim is
2019 always found. Since this directory is added to $PATH it 2019 normally found. Since this directory is added to $PATH it
2020 should also work to execute it |win32-PATH|. 2020 should also work to execute it |win32-PATH|. This can be
2021 disabled by setting the $NoDefaultCurrentDirectoryInExePath
2022 environment variable. *NoDefaultCurrentDirectoryInExePath*
2021 The result is a Number: 2023 The result is a Number:
2022 1 exists 2024 1 exists
2023 0 does not exist 2025 0 does not exist
2024 -1 not implemented on this system 2026 -1 not implemented on this system
2025 |exepath()| can be used to get the full path of an executable. 2027 |exepath()| can be used to get the full path of an executable.