On 20/11/2014 09:18, Christian Brabandt wrote:
> Am 2014-11-19 23:27, schrieb Jack Donohue:
>> These are the plugins in my plugin directory:
>>
>> getscriptPlugin.vim
>> gzip.vim
>> matchparen.vim
>> netrwPlugin.vim
>> rrhelper.vim
>> spellfile.vim
>> tarPlugin.vim
>> tohtml.vim
>> vimballPlugin.vim
>> zipPlugin.vim
>>
>> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:38:33)
>> MS-Windows 32-bit GUI version with OLE support
>> Compiled by mool@tororo
>> Big version with GUI. Features included (+) or not (-):
>> +arabic +ex_extra +mouseshape +syntax
>> +autocmd +extra_search +multi_byte_ime/dyn
>> +tag_binary
>> +balloon_eval +farsi +multi_lang
>> +tag_old_static
>> +browse +file_in_path -mzscheme
>> -tag_any_white
>> ++builtin_terms +find_in_path +netbeans_intg +tcl/dyn
>> +byte_offset +float +ole -tgetent
>> +cindent +folding +path_extra
>> -termresponse
>> +clientserver -footer +perl/dyn
>> +textobjects
>> +clipboard +gettext/dyn +persistent_undo +title
>> +cmdline_compl -hangul_input -postscript +toolbar
>> +cmdline_hist +iconv/dyn +printer
>> +user_commands
>> +cmdline_info +insert_expand -profile +vertsplit
>> +comments +jumplist +python/dyn
>> +virtualedit
>> +conceal +keymap +python3/dyn +visual
>> +cryptv +langmap +quickfix
>> +visualextra
>> +cscope +libcall +reltime +viminfo
>> +cursorbind +linebreak +rightleft +vreplace
>> +cursorshape +lispindent +ruby/dyn
>> +wildignore
>> +dialog_con_gui +listcmds +scrollbind +wildmenu
>> +diff +localmap +signs +windows
>> +digraphs -lua +smartindent
>> +writebackup
>> -dnd +menu -sniff -xfontset
>> -ebcdic +mksession +startuptime -xim
>> +emacs_tags +modify_fname +statusline
>> -xterm_save
>> +eval +mouse -sun_workshop +xpm_w32
>> system vimrc file: "$VIMvimrc"
>> user vimrc file: "$HOME_vimrc"
>> 2nd user vimrc file: "$HOMEvimfilesvimrc"
>> 3rd user vimrc file: "$VIM_vimrc"
>> user exrc file: "$HOME_exrc"
>> 2nd user exrc file: "$VIM_exrc"
>> system gvimrc file: "$VIMgvimrc"
>> user gvimrc file: "$HOME_gvimrc"
>> 2nd user gvimrc file: "$HOMEvimfilesgvimrc"
>> 3rd user gvimrc file: "$VIM_gvimrc"
>> system menu file: "$VIMRUNTIMEmenu.vim"
>>
>> Do you think running a 32 bit version on 64 bit windows 7 had anything
>> to do with it?
>
> Yes, I think this is possible. Also it might depend on the compiler. I
> remember
> some discussions, saying that when using visual studio it is faster than
> using the mingw or cygwin
> gcc. That's why I asked for the complete :version output. So you might
> want to test different Vim versions.
>
> Also I just noted that when the runtime files live on a network share
> (as has been the case for me)
> loading those files is a lot slower.
An optimised 32bit build on Win7 x64 is nice and quick. I can get a
5sec startuptime if I do a non-optimised build. The bulk of the time
was spent sourcing synload.vim which doesn't tie up to the reported
startuptime results. That appeared to show time spent in preparing the
GUI - all that happens at that time is initialising OLE and loading a
dll to get at some entry points. I'm not an OLE expert so don't know
what may affect that but the code looks small and simple. Loading a dll
should be quick.
I build with MSVC, it may be that alternate compilers and their runtime
libraries cause slow downs. Unfortunately the compiler used is not
reported by version, perhaps it should to help with these types of problems.
TTFN
Mike
--
Not afraid of heights - afraid of widths.
--
--
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/d/optout.
No comments:
Post a Comment