You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feedback #1875: command-t-1.2.1.vba fails to unpack under vim-7.3, ruby-1.9

Kind feedback
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

This may be a problem with the way I compiled vim-7.3, but when I try to source command-t-1.2.1.vba, I get the following errors: 

Error detected while processing function vimball#Vimball:
line  131:
E474: Invalid argument: silent w! ++enc=7 /home/me/.vim/ruby/command-t/controller.rb
...

I'll get one E474 error for each file in the archive.

The directories are created in /home/me/.vim/, but no files are populated.

I compiled vim-7.3 myself on a Centos box. Below is the output from vim --version.

Is there something not configured correctly with my compiled vim? 

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Sep 15 2011 14:06:43)
Compiled by me@host
Normal version without GUI.  Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent 
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
-conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con +diff +digraphs 
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path 
+find_in_path +float +folding -footer +fork() +gettext -hangul_input -iconv 
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent 
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape 
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse 
+mouse_xterm -multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype 
+path_extra +perl +persistent_undo +postscript +printer -profile +python 
-python3 +quickfix +reltime -rightleft +ruby +scrollbind +signs +smartindent 
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary 
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
 -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo 
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
 -xterm_clipboard -xterm_save 
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/apps/dev/packages/vim-7.3.001/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H     -g -O2 -D_FORTIFY_SOURCE=1     -I/apps/dev/packages/ruby-1.9.2.001/include/ruby-1.9.1 -I/apps/dev/packages/ruby-1.9.2.001/include/ruby-1.9.1/i686-linux -DRUBY_VERSION=19 
Linking: gcc   -L.  -rdynamic -Wl,-export-dynamic  -Wl,-E   -L/usr/local/lib -o vim       -ltermcap -lselinux     -Wl,-E  -fstack-protector -L/usr/local/lib  -L/product01/apps/dev/packages/perl-5.14.001/lib/5.14.1/i686-linux/CORE -lperl -lutil -lc -L/apps/dev/packages/python-2.7.2.001/lib/python2.7/config -lpython2.7 -lutil -Xlinker -export-dynamic   -Wl,-R -Wl,/apps/dev/packages/ruby-1.9.2.001/lib -L/apps/dev/packages/ruby-1.9.2.001/lib -lruby-static -lrt -lcrypt -lm

Comments

  1. Greg Hurrell

    If the Vimball install is giving you problems, you could try installing via Pathogen (which is generally superior anyway).

  2. Greg Hurrell

    Closing due to lack of activity.

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
  4. Grzegorz Dolatowski

    This error occurs when vimball uses 'enc' option, but vim was not compiled with multi_byte feature, which is required by it. This is the case in the above example. Check 'help encoding' for more details.

    To enable multi_byte feature run ./configure with --enable-multibyte option when compiling vim from sources.

Add a comment

Comments are now closed for this issue.

Menu