thanks Ben.
that works as expected, not quite handy though...but still good.
On Fri, Dec 20, 2013 at 9:08 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
On Friday, December 20, 2013 7:29:52 PM UTC-6, ping wrote:> [snip]
>
> but if it look at vimgrep, it actually provide very little control of on what files your search is running on -- mostly you either have to list all files manually, or you have to put all files in one folder and using "*" or "**" to work on them.
>
>Woah, I didn't know about ##!
> apparently vimgrep doen't care about buffers/tabs so far.
>
>
> the only thing close is the "##", which is the list of all files as vim args when it was invoked.
> but that is not always precise either. since something you changed the mind after you worked on these files, but only want to check some of the files , which you assigned with a tab for each.
You could actually use this to accomplish what you want, because you can modify the argument list after startup.
See :help :argadd, :argdel, and other stuff in that section.
--
--
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/groups/opt_out.
--
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/groups/opt_out.
No comments:
Post a Comment