James McCoy wrote:
> This just uses the existing logic in mch_can_exe to populate a buffer with the
> absolute path to the binary. The Windows code was already walking
> $PATH, so it seems pointless not to actually use the information.
Quite a few years ago I was debugging a Vim that started up slowly. It
turned out that walking through $PATH was the main cause for that. So I
don't want to walk through $PATH when not really needed.
Shells do a lot of caching to avoid walking through $PATH, for good
reasons.
On MS-Windows we need to check the extensions. I didn't realize it also
goes through $PATH, hidden in executable_exists(). Thus the use_path
argument is used in a wrong way. I'll fix that.
> There's no reason not to behave the same way on non-Windows platforms,
> so change the code to always use mch_can_exe. With a small fix to how
> mch_can_exe determines whether FullName_save is needed.
I'll merge your change with the fix for Windows.
--
hundred-and-one symptoms of being an internet addict:
53. To find out what time it is, you send yourself an e-mail and check the
"Date:" field.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
