Thursday, October 1, 2015

Re: file patterns for argument list

On Thu, Oct 1, 2015 at 8:58 PM, Benjamin Fritz <fritzophrenic@gmail.com> wrote:
> Today I discovered that this works to add both file.h and file.cpp to the
> arg list:
>
> :args file.*{cpp,h}
>
> But this doesn't work:
>
> :args file.{cpp,h}
>
> The second variant just adds the (non-existent) "file.{cpp,h}" file name
> (with a literal "{h,cpp}" in the name) to the arg list.
>
> Why?
>

It might be related to what I read in $VIMRUNTIME/doc/cmdline.txt
lines 940 sqq. (some lines below the helptag *extension-removal*), as
follows:

Note: Where a file name is expected wildcards expansion is done. On Unix the
shell is used for this, unless it can be done internally (for speed).
Unless in |restricted-mode|, backticks work also, like in >
:n `echo *.c`
But expansion is only done if there are any wildcards before expanding the
'%', '#', etc.. This avoids expanding wildcards inside a file name.



Best regards,
Tony.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment