On 15/09/09 01:54, Hari Krishna Dara wrote:
[...]
> Sorry, it should be -nargs, not -args. The completion allows you to
> complete filenames, by pressing, though won't help much with the
> wildcards. BTW, I don't actually know if wildcards can be used in
> :args.
>
According to the help they can:
Hello,
"Daniel Fetchinson" wrote :
> This in itself is pretty cool, but now I'd like to make something
> even cooler by hooking up a custom function to do this. This is
> where I'm currently failing. What I'd like to see is when I type
>
> :msplit filename*
If I may, I provide a plugin that a
>> The :all ends up giving me all the .sql *and all the .py files*
>> when all I really want is all the .sql files.
>
> That's why everyone else in the thread has been suggesting using :args
> instead of :argadd ;-)
>
> Of course, :args is worse if you're the sort of person who actually
> uses
On Mon, Sep 14, 2009 at 4:45 PM, Daniel Fetchinson
wrote:
>>
>> Try this (untested):
>>
>> function! Msplit(...)
>> if a:0 > 0
>> exec args join(a:000, ' ')
>> endif
>> all
>> endfunction
>>
>> command! -args=* -complete=file Msplit :call Msplit()
>
> This, in its current form, gives an
On Mon, Sep 14, 2009 at 6:27 PM, Tim Chase wrote:
>
>> :msplit filename*
>>
>> then this should be equivalent to
>>
>> :args filename*
>> :all
>
> The problem I have with :all is that it opens *all* the
> arguments. I frequently find myself in the position where I've
> started vim with something
On 2009-09-14, Daniel Fetchinson wrote:
> >> >>> I'm regularly doing :split filename1 followed by :split filename2
> >> >>> followed by :split filename3 and was trying to do :split filename* but
> >> >>> this didn't work. The goal would be to split the window in as many
> >> >>> pieces as the numb
On 9/14/09, Daniel Fetchinson wrote:
>>> >>> I'm regularly doing :split filename1 followed by :split filename2
>>> >>> followed by :split filename3 and was trying to do :split filename*
>>> >>> but
>>> >>> this didn't work. The goal would be to split the window in as many
>>> >>> pieces as the nu
>> :msplit filename*
>>
>> then this should be equivalent to
>>
>> :args filename*
>> :all
>
> The problem I have with :all is that it opens *all* the
> arguments. I frequently find myself in the position where I've
> started vim with something like
>
>vim *.py
>
> and have all my project's p
> I'm regularly doing :split filename1 followed by :split filename2
> followed by :split filename3 and was trying to do :split filename* but
> this didn't work. The goal would be to split the window in as many
> pieces as the number of files that match filename* and have each of
>>
>> >>> I'm regularly doing :split filename1 followed by :split filename2
>> >>> followed by :split filename3 and was trying to do :split filename* but
>> >>> this didn't work. The goal would be to split the window in as many
>> >>> pieces as the number of files that match filename* and have each o
On Mon, Sep 14, 2009 at 2:47 PM, Daniel Fetchinson
wrote:
>
I'm regularly doing :split filename1 followed by :split filename2
followed by :split filename3 and was trying to do :split filename* but
this didn't work. The goal would be to split the window in as many
pieces as the
> :msplit filename*
>
> then this should be equivalent to
>
> :args filename*
> :all
The problem I have with :all is that it opens *all* the
arguments. I frequently find myself in the position where I've
started vim with something like
vim *.py
and have all my project's python files ope
On 2009-09-14, Daniel Fetchinson wrote:
> >>> I'm regularly doing :split filename1 followed by :split filename2
> >>> followed by :split filename3 and was trying to do :split filename* but
> >>> this didn't work. The goal would be to split the window in as many
> >>> pieces as the number of files
>>> I'm regularly doing :split filename1 followed by :split filename2
>>> followed by :split filename3 and was trying to do :split filename* but
>>> this didn't work. The goal would be to split the window in as many
>>> pieces as the number of files that match filename* and have each of
>>> the ma
>> I'm regularly doing :split filename1 followed by :split filename2
>> followed by :split filename3 and was trying to do :split filename* but
>> this didn't work. The goal would be to split the window in as many
>> pieces as the number of files that match filename* and have each of
>> the matchin
Gary Johnson wrote:
> On 2009-09-12, Daniel Fetchinson wrote:
>> Hi vimmers,
>>
>> I'm regularly doing :split filename1 followed by :split filename2
>> followed by :split filename3 and was trying to do :split filename* but
>> this didn't work. The goal would be to split the window in as many
>> pi
On 2009-09-12, Daniel Fetchinson wrote:
> Hi vimmers,
>
> I'm regularly doing :split filename1 followed by :split filename2
> followed by :split filename3 and was trying to do :split filename* but
> this didn't work. The goal would be to split the window in as many
> pieces as the number of files
Hi vimmers,
I'm regularly doing :split filename1 followed by :split filename2
followed by :split filename3 and was trying to do :split filename* but
this didn't work. The goal would be to split the window in as many
pieces as the number of files that match filename* and have each of
the matching
18 matches
Mail list logo
