Wednesday, February 13, 2013

Re: ios vim and plugins

Hi Eric!

On Mo, 11 Feb 2013, Eric Weir wrote:

>
> On Feb 10, 2013, at 9:23 PM, Marcin Szamotulski wrote:
>
> >> It's not gonna be so easy. Even with a relatively small number of plugins, there's a horrendous number of files to be listed. E.g., every one of my plugins has a .git folder associated with it. The number of files in just one of those is pretty big.
> >>
> >> Or is there a way to get my system---mac or vim---to write the paths to a range of files?
> >
> > That's what for are scripting languages. You can use bash, python, perl
> > or even VimL to do that. With Vim you can do the following:
> >
> > set nomore
> > redir @a
> > echo globpath('~/.vim', '**')
> > redir END
> >
> > Now paste the register a into a new buffer and review the list. It
> > should skip all the dot files (like .git, etc).
>
> Thanks, Marcin. I'm just a dumb writer. I don't know any scripting language. [Perhaps I should start.]
>
> From what Bill says, looks like I won't be able to use this for the purpose I had in mind, but I think I'll give it a try. It might be useful down the road.
>
> Is it possible to force inclusion of dot files? In the use I had in mind the .git files were the main challenge. There were several. Each associated with a plugin. Each with many files and more layers of folders than the plugins.
>

You don't need the .git files to make the plugin work.

Mit freundlichen Grüßen
Christian
--
Das Glück deines Lebens hängt von der Beschaffenheit deiner Gedanken
ab.
-- Mark Aurel (römischer Kaiser, 121-180)

--
--
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: