On Nov 12, 2007 9:16 AM, Nikolai Weibull <[EMAIL PROTECTED]> wrote: > > On Nov 12, 2007 3:09 PM, Vladimir Marek <[EMAIL PROTECTED]> wrote: > > > > Another issue is that there's doesn't seem to be a way to escape a > > > comma inside a brace expansion. Neither two commas in a row or a > > > backslash seem to generate a comma. > > > > glob behaves depending on your shell settings. Out of my experience, > > best is csh or tcsh, where glob works reliably. Worst is sh. > > Vim's glob() function doesn't depend on the shell.
Actually, it does. (gdb) bt #0 call_shell at misc2.c:2946 #1 0x0813fcac in mch_expand_wildcards at os_unix.c:5256 #2 0x0810595a in gen_expand_wildcards at misc1.c:9130 #3 0x0810501c in expand_wildcards at misc1.c:8424 #4 0x080b8c31 in ExpandFromContext at ex_getln.c:4331 #5 0x080b7706 in ExpandOne at ex_getln.c:3430 #6 0x0807eb4a in f_glob at eval.c:10681 That's why :help glob() points to :help wildcards, which says "Which wildcards are supported depends on the system." Though, for at least tcsh and zsh as well as sh, the extra / is present on the expansion you listed, so perhaps it is a buglet. ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
