Re: Vim startup profiling

Hi, 2017/10/25 Wed 21:28:50 UTC+9 Christian Brabandt wrote: > Hi Ken, > I briefly looked at your patch and have some feedback. > > On Mi, 25 Okt 2017, Ken Takata wrote: > > > Changes are: > > * Merge the two patches into one. > > * Update the document. > > * Rename the global variable

Re: Vim startup profiling

Hi Ken, I briefly looked at your patch and have some feedback. On Mi, 25 Okt 2017, Ken Takata wrote: > Changes are: > * Merge the two patches into one. > * Update the document. > * Rename the global variable `do_globpath_menus` to `do_lazyload_menus`. > I'm still wondering what is the best

Re: Vim startup profiling

Hi, 2017/10/25 Wed 6:20:09 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > > > 2017/5/26 Fri 22:36:40 UTC+9 Ken Takata wrote: > > > > > > 096.000 047.000 044.000: sourcing D:\Logiciels\Vim\vim80/menu.vim > > > > > > 096.000 072.000 025.000: sourcing > > > > > >

Re: Vim startup profiling

Ken Takata wrote: > > > 2017/5/26 Fri 22:36:40 UTC+9 Ken Takata wrote: > > > > > 096.000 047.000 044.000: sourcing D:\Logiciels\Vim\vim80/menu.vim > > > > > 096.000 072.000 025.000: sourcing > > > > > D:\Logiciels\Vim\vim80\filetype.vim > > > > > > > > menu.vim uses `globpath()` to search

Re: Vim startup profiling

Hi Bram, 2017/10/24 Tue 5:45:40 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > 2017/5/26 Fri 22:36:40 UTC+9 Ken Takata wrote: > > > > 096.000 047.000 044.000: sourcing D:\Logiciels\Vim\vim80/menu.vim > > > > 096.000 072.000 025.000: sourcing D:\Logiciels\Vim\vim80\filetype.vim > > >

Re: Vim startup profiling

Ken Takata wrote: > 2017/5/26 Fri 22:36:40 UTC+9 Ken Takata wrote: > > > 096.000 047.000 044.000: sourcing D:\Logiciels\Vim\vim80/menu.vim > > > 096.000 072.000 025.000: sourcing D:\Logiciels\Vim\vim80\filetype.vim > > > > menu.vim uses `globpath()` to search some kind of files under the >

Re: Vim startup profiling

Hi, 2017/5/26 Fri 22:36:40 UTC+9 Ken Takata wrote: > > 096.000 047.000 044.000: sourcing D:\Logiciels\Vim\vim80/menu.vim > > 096.000 072.000 025.000: sourcing D:\Logiciels\Vim\vim80\filetype.vim > > menu.vim uses `globpath()` to search some kind of files under the runtimepath. > If you

Re: Vim startup profiling

On Fr, 26 Mai 2017, Ken Takata wrote: > > Ok I save 100ms using the plugin manager vim-plug but not enough for me. > > Is anyone can advise me or explain to me why some files are loaded twice > > and take twice or more times N msec: > > - vim80/menu.vim > > - vim80\filetype.vim > > > 096.000

Re: Vim startup profiling

Hi, 2017/5/24 Wed 17:39:34 UTC+9 Ni Va wrote: > Le mardi 23 mai 2017 21:46:01 UTC+2, Ni Va a écrit : > > Le mardi 23 mai 2017 18:14:24 UTC+2, MarcWeber a écrit : > > > > Thank you > > > Sped up by using a plugin manager supporting lazy loading or as needed > > > (vim-addon-manager/Neobundle

Re: Vim startup profiling

Le mercredi 24 mai 2017 21:54:12 UTC+2, Christian Brabandt a écrit : > On Mi, 24 Mai 2017, Antony Scriven wrote: > > > Your colorscheme or vimrc or both appears to be causing > > syncolor.vim to go bananas. I'd take a look at the code > > there to find out what's going on. filetype.vim and

Re: Vim startup profiling

On Mi, 24 Mai 2017, Antony Scriven wrote: > Your colorscheme or vimrc or both appears to be causing > syncolor.vim to go bananas. I'd take a look at the code > there to find out what's going on. filetype.vim and menu.vim > are just big. You can disable loading menu.vim with `set > guioptions+=M`

Re: Vim startup profiling

Le mercredi 24 mai 2017 11:01:31 UTC+2, Dominique Pelle a écrit : > Ni Va : > > > Le mardi 23 mai 2017 21:46:01 UTC+2, Ni Va a écrit : > >> Le mardi 23 mai 2017 18:14:24 UTC+2, MarcWeber a écrit : > >> > > Thank you > >> > Sped up by using a plugin manager supporting lazy

Re: Vim startup profiling

> Ok I save 100ms using the plugin manager vim-plug but not enough for me. > Is anyone can advise me or explain to me why some files are loaded twice and > take twice or more times N msec: > - vim80/menu.vim > - vim80\filetype.vim I never compared vimplug vs VAM, but I'd be interested in it.

Re: Vim startup profiling

Ni Va : > Le mardi 23 mai 2017 21:46:01 UTC+2, Ni Va a écrit : >> Le mardi 23 mai 2017 18:14:24 UTC+2, MarcWeber a écrit : >> > > Thank you >> > Sped up by using a plugin manager supporting lazy loading or as needed >> > (vim-addon-manager/Neobundle maybe more). >> > >> >

Re: Vim startup profiling

Your colorscheme or vimrc or both appears to be causing syncolor.vim to go bananas. I'd take a look at the code there to find out what's going on. filetype.vim and menu.vim are just big. You can disable loading menu.vim with `set guioptions+=M` if you don't need it. --Antony 2017-05-24 9:39

Re: Vim startup profiling

Le mardi 23 mai 2017 21:46:01 UTC+2, Ni Va a écrit : > Le mardi 23 mai 2017 18:14:24 UTC+2, MarcWeber a écrit : > > > Thank you > > Sped up by using a plugin manager supporting lazy loading or as needed > > (vim-addon-manager/Neobundle maybe more). > > > > Typically sourcing twice is not a

Re: Vim startup profiling

Le mardi 23 mai 2017 18:14:24 UTC+2, MarcWeber a écrit : > > Thank you > Sped up by using a plugin manager supporting lazy loading or as needed > (vim-addon-manager/Neobundle maybe more). > > Typically sourcing twice is not a problem, often guard [1] like guard > has been setup which is a quick

Re: Vim startup profiling

> Thank you Sped up by using a plugin manager supporting lazy loading or as needed (vim-addon-manager/Neobundle maybe more). Typically sourcing twice is not a problem, often guard [1] like guard has been setup which is a quick workraound which immediately saves most time. Marc Weber [1] if