error thrown when enter insert mode first time in MacVim

[liuchengxu]

:version in MacVim:

VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Nov  6 2017 17:41:12)
macOS version
Included patches: 1-1272
Compiled by Homebrew
Huge version with MacVim GUI.  Features included (+) or not (-):
+acl             +comments        +extra_search    +jumplist        +mouseshape      +odbeditor       +scrollbind      +termresponse    +wildmenu
+arabic          +conceal         +farsi           +keymap          +mouse_dec       +packages        +signs           +textobjects     +windows
+autocmd         +cryptv          +file_in_path    +lambda          -mouse_gpm       +path_extra      +smartindent     +timers          +writebackup
+balloon_eval    +cscope          +find_in_path    +langmap         -mouse_jsbterm   +perl            +startuptime     +title           -X11
+browse          +cursorbind      +float           +libcall         +mouse_netterm   +persistent_undo +statusline      +toolbar         -xfontset
++builtin_terms  +cursorshape     +folding         +linebreak       +mouse_sgr       +postscript      -sun_workshop    +transparency    +xim
+byte_offset     +dialog_con_gui  -footer          +lispindent      -mouse_sysmouse  +printer         +syntax          +user_commands   -xpm
+channel         +diff            +fork()          +listcmds        +mouse_urxvt     +profile         +tag_binary      +vertsplit       -xsmp
+cindent         +digraphs        +fullscreen      +localmap        +mouse_xterm     +python          +tag_old_static  +virtualedit     -xterm_clipboard
+clientserver    +dnd             -gettext         -lua             +multi_byte      -python3         -tag_any_white   +visual          -xterm_save
+clipboard       -ebcdic          -hangul_input    +menu            +multi_lang      +quickfix        -tcl             +visualextra
+cmdline_compl   +emacs_tags      +iconv           +mksession       -mzscheme        +reltime         +termguicolors   +viminfo
+cmdline_hist    +eval            +insert_expand   +modify_fname    +netbeans_intg   +rightleft       +terminal        +vreplace
+cmdline_info    +ex_extra        +job             +mouse           +num64           +ruby            +terminfo        +wildignore
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X -DMACOS_X_DARWIN  -F/usr/local/opt/python/Frame
works -I/usr/local/Cellar/python/2.7.14/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I/usr/local/Cellar/python/2.7.14/Frameworks/Python.framewor
k/Versions/2.7/include/python2.7 -fno-strict-aliasing -fno-common -dynamic -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Devel
oper/SDKs/MacOSX10.12.sdk -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Tk.fr
amework/Versions/8.5/Headers -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -L/usr/local/lib -L. -L/usr/local/lib -F/usr/local/opt/python/Frameworks -L/usr/local/opt/python/Frameworks/Python.framework/Versions/2.7/
lib/python2.7/config -lpython2.7 -framework CoreFoundation -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv -framework A
ppKit   -fstack-protector  -L/System/Library/Perl/5.18/darwin-thread-multi-2level/CORE -lperl -F/usr/local/opt/python/Frameworks -framework Python   -framework
 Ruby

When I enter insert mode first time (i)in MacVim, the errors above are thrown. But this issue occurs only once. Afterwards, completor.vim can still work as normal. Any tips?

[maralla]

I think this problem may be caused by completor-neosnippet. I pushed a commit to that repo to improve the problem.

[liuchengxu]

Thanks! It's fixed.