Re: Vim Lua and such

Nazri Ramliy wrote:

> On Mon, Jul 8, 2013 at 12:03 AM, <meino.cramer@gmx.de> wrote:
>> The longest line of the dbfile is 71 characters long. So I think, at
>> least this is no problem ;)
>>
>> It seems to be a problem with one of the plugins.
>> Lua itsself read/interprets the dbfile without a second of delay,
>> though.
>>
>> I am not very motivated to step through all of my plugins switch them
>> off/on one by one... :-/
>
> Using perf may help finding out where vim is spending most of the time on:
>
> 1. Edit Makefile and uncomment "#CFLAGS = -g"
> 2. Compile vim
> 3. in src dir:
>
> $ perf record ./vim -c 'set re=0' dbfile.lua
> <Hit Ctrl+C so that vim stops whatever it is busy doing, hopefully

Better use the -g flag to get backtrace recording:

$ perf record -g ./vim -c 'set re=0' dbfile.lua
<Hit Ctrl+C so that vim stops whatever it is busy doing, hopefully

$ perf report -i perf.data

Then in perf report, you can move to functions with arrow
keys and press enter to view stacks.

Dominique

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