Sunday, December 13, 2015

Why is :E an ambiguous command after upgrading to patches through 965?

Win7-64 bit Pro, Vim 7.4 with patches 1-965.

I thought I would update Vim to the latest patches I could find. I
got the Windows installation binary from
https://bintray.com/veegee/generic/vim_x64/#

Now that I have done this update, when I use :E to open the file
explorer I get "E464: Ambiguous use of user-defined command."
However, :Ex works.

Can someone tell me what new feature has been added with this update
that now makes :E an ambiguous command? The full version info
follows:

:version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 11 2015 11:38:48)
MS-Windows 64-bit GUI version with OLE support
Included patches: 1-965
Compiled by veegee@veegee-win8
Huge version with GUI. Features included (+) or not (-):
+acl +clipboard +cursorshape +ex_extra
-hangul_input +listcmds +multi_lang +profile
+smartindent -tcl +visual -xim
+arabic +cmdline_compl +dialog_con_gui +extra_search
+iconv/dyn +localmap -mzscheme +python/dyn
-sniff -tgetent +visualextra -xterm_save
+autocmd +cmdline_hist +diff +farsi
+insert_expand +lua/dyn +netbeans_intg +python3/dyn
+startuptime -termresponse +viminfo -xpm_w32
+balloon_eval +cmdline_info +digraphs +file_in_path
+jumplist +menu +ole +quickfix
+statusline +textobjects +vreplace
+browse +comments -directx +find_in_path
+keymap +mksession +path_extra +reltime
-sun_workshop +title +wildignore
++builtin_terms +conceal -dnd +float
+langmap +modify_fname -perl +rightleft
+syntax +toolbar +wildmenu
+byte_offset +cryptv -ebcdic +folding
+libcall +mouse +persistent_undo -ruby
+tag_binary +user_commands +windows
+cindent +cscope +emacs_tags -footer
+linebreak +mouseshape -postscript +scrollbind
+tag_old_static +vertsplit +writebackup
+clientserver +cursorbind +eval +gettext/dyn
+lispindent +multi_byte +printer +signs
-tag_any_white +virtualedit -xfontset
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$HOME\vimfiles\vimrc"
3rd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DWINVER=0x0400
-D_WIN32_WINNT=0x0400 /Fo.\ObjGOUYHAMD64/ /Ox -DNDEBUG /Zl /MT
-DFEAT_OLE -DFEAT_GUI
_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT -DFEAT_LUA -DDYNAMIC_LUA
-DDYNAMIC_LUA_DLL=\"lua52.dll\" -DFEAT_PYTHON -DDYNAMIC_PYTHON
-DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
-DDYNAMIC_PY
THON3_DLL=\"python35.dll\" -DFEAT_HUGE /Fd.\ObjGOUYHAMD64/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows oldnames.lib
kernel32.lib advapi32.lib shell32.lib gdi32.lib comdlg32.lib
ole32.lib uuid.lib /machine:AMD64 gdi32.lib version.lib winspool.lib
comctl32.lib ad
vapi32.lib shell32.lib /machine:AMD64 libcmt.lib oleaut32.lib
user32.lib /nodefaultlib:lua52.lib /nodefaultlib:python27.lib
/nodefaultlib:python35.lib WSock32.lib /PDB:gvim.pdb -debug

--
boB

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