James Vega wrote:
> When running tests in my build environment, I noticed that test73 kept
> failing while it would work fine in my normal environment. Turns out
> this is because my build environment uses dash[0] for /bin/sh, which
> doesn't support ** wildcards (since they're not specified by POSIX).
>
> Poking around, I see that unix_expandpath handles ** regardless of shell
> by doing its own expansion. Would it make sense to use unix_expandpath
> to handle the ** when mch_expand_wildcards needs STYLE_VIMGLOB ('shell'
> is "sh") or STYLE_ECHO (unknown shell)?
When it gets to STYLE_VIMGLOB or STYLE_ECHO this means the shell must be
used to expand wildcards. Trying unix_expandpath() should already have
happened. That's because using the shell is a last resort, as it's
quite slow.
I don't see the sequence of calls that would lead to this. Perhaps it
depends on some setting?
--
How To Keep A Healthy Level Of Insanity:
16. Have your coworkers address you by your wrestling name, Rock Hard Kim.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.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
