On Saturday, November 8, 2014 1:13:00 AM UTC+8, Tim Lebedkov wrote:
> Hi,
>
> the repository at https://github.com/gpwen/vim-installer-mui2/wiki is
> interesting, but the changes there do not help as they will probably never be
> merged.
>
> My next patch will introduce MUI2.
>
What is your o
On Fri, Nov 07, 2014 at 06:57:00PM -0800, Yuri wrote:
> I believe this line should work:
> $ vim "+normal(G|)"
> But it doesn't place the cursor to the right position.
That's because you've added unnecessary ( and ) motions. Try just
vim '+normal G|'
:normal is an ex command, not a function
I believe this line should work:
$ vim "+normal(G|)"
But it doesn't place the cursor to the right position.
In normal mode, pressing G| brings cursor there.
"+normal(cmds)" as a command line argument should execute cmds the same
way after the file is opened. Where I am wrong?
Yuri
--
--
You
Micha wrote:
> I just ran into the following small bug.
> Suppose you are editing a buffer for which the tag 'tag_foo' is defined.
> Now, enter the following command ':tag/foo' followed by to trigger
> autocompletion of the command based on the existing tags.
> This will replace '/foo' by 'tag_
Christian Brabandt wrote:
> On Di, 28 Okt 2014, Ingo Karkat wrote:
>
> > Well, then perhaps a separate :bvimgrep[add] set of commands would be
> > better than overloading the existing commands:
> >
> > :bvimgrep[!] /{pattern}/[g][j] [bufname]
> > :bvimgrep[!] /{pattern}/[g][j] N1 N2 ...
>
> Ok
Tomas Mozes wrote:
> On Friday, June 14, 2013 2:58:48 PM UTC+2, Christian Wellenbrock wrote:
> > I attached a yaml file as example. Please open it with vim to test the
> > highlighting speed. Scolling and searching is very slow. Tested on vim
> > 7.3.1106
>
> Still valid for 7.4.488.
>
> This
Hi,
the repository at https://github.com/gpwen/vim-installer-mui2/wiki is
interesting, but the changes there do not help as they will probably never be
merged.
My next patch will introduce MUI2.
Am Donnerstag, 6. November 2014 09:26:09 UTC+1 schrieb KF Leong:
> On Wednesday, September 24, 2014
Hi,
I just ran into the following small bug.
Suppose you are editing a buffer for which the tag 'tag_foo' is defined.
Now, enter the following command ':tag/foo' followed by to trigger
autocompletion of the command based on the existing tags.
This will replace '/foo' by 'tag_foo', resulting in t
Christian Brabandt wrote:
> Dominique, On Fr, 07 Nov 2014, Christian Brabandt wrote:
>> On Do, 06 Nov 2014, Dominique Pellé wrote:
>> > Valgrind detects a bug in Vim-7.4.507 when doing:
>> >
>> > $ valgrind vim -c ':setfiletype c' -c 'call feedkeys("i// foo\\")'
>>
>> While I do not see that error
On Di, 28 Okt 2014, Ingo Karkat wrote:
> Well, then perhaps a separate :bvimgrep[add] set of commands would be
> better than overloading the existing commands:
>
> :bvimgrep[!] /{pattern}/[g][j] [bufname]
> :bvimgrep[!] /{pattern}/[g][j] N1 N2 ...
Okay. So here is a patch, implementing the :bvim
Dominique, On Fr, 07 Nov 2014, Christian Brabandt wrote:
> On Do, 06 Nov 2014, Dominique Pellé wrote:
> > Valgrind detects a bug in Vim-7.4.507 when doing:
> >
> > $ valgrind vim -c ':setfiletype c' -c 'call feedkeys("i// foo\\")'
>
> While I do not see that error with valgrind, I noticed that th
On Friday, June 14, 2013 2:58:48 PM UTC+2, Christian Wellenbrock wrote:
> I attached a yaml file as example. Please open it with vim to test the
> highlighting speed. Scolling and searching is very slow. Tested on vim
> 7.3.1106
Still valid for 7.4.488.
This seems to work much better:
https://g
Hi,
On Do, 06 Nov 2014, Dominique Pellé wrote:
> Valgrind detects a bug in Vim-7.4.507 when doing:
>
> $ valgrind vim -c ':setfiletype c' -c 'call feedkeys("i// foo\\")'
While I do not see that error with valgrind, I noticed that the cursor
now moved too much in the other direction. I'll check
13 matches
Mail list logo
