Opened 9 years ago

Closed 9 years ago

#47643 closed defect (invalid)

vim 7.4 reports 7.3 version once installed

Reported by: eliseo.martinez@… Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port: vim

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I'm installing vim 7.4 port:

~ ❯❯❯ sudo port install vim
--->  Computing dependencies for vim
--->  Fetching archive for vim
--->  Attempting to fetch vim-7.4.258_1+huge.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/vim
--->  Attempting to fetch vim-7.4.258_1+huge.darwin_14.x86_64.tbz2.rmd160 from http://lil.fr.packages.macports.org/vim
--->  Installing vim @7.4.258_1+huge
--->  Activating vim @7.4.258_1+huge
--->  Cleaning vim
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.

Everything seems to go ok, but when I enter vim:

YouCompleteMe unavailable: requires Vim 7.3.584+
The EnhancedDiff Plugin needs at least a Vim version 7.4
Press ENTER or type command to continue

In fact, version reported within vim is:

:version                                                                                                            
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov  5 2014 21:00:28)
Compiled by root@apple.com
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/dyn -python3 +quickfix +reltime -rightleft +ruby/dyn +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: "/usr/share/vim"
Compilation: gcc -c -I. -D_FORTIFY_SOURCE=0 -Iproto -DHAVE_CONFIG_H -arch i386 -arch x86_64 -g -Os -pipe
Linking: gcc -arch i386 -arch x86_64 -o vim -lncurses

Weird...

Thanks, Eliseo.

Change History (5)

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Owner: changed from macports-tickets@… to raimue@…
Port: vim added

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

It looks like you have successfully installed the MacPorts version of vim, but are still running the Apple version of vim.

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Have you already tried running hash -r, or closing the terminal window and making a new one?

If yes, what is the value of your PATH environment variable? Does /opt/local/bin come first in it, or at least before /usr/bin?

comment:4 Changed 9 years ago by eliseo.martinez@…

Gosh. I'm really sorry about this. I tried again now and it worked perfectly (probably because I opened a new terminal window). But that shouldn't be necessary, should it? I mean, my $PATH is correct (/opt/local/bin before /usr/bin and others). So, once sudo port install finishes, it should locate the macports one first... I don't really know what happened here. This can be closed. Thanks.

comment:5 Changed 9 years ago by raimue (Rainer Müller)

Resolution: invalid
Status: newclosed

You ran 'vim' before installing the vim port and it found the binary at /usr/bin/vim. Your shell remembers the path where it found the binary for a command and it will just use the same path if you type the same command again. The shell will not notice any new binary in PATH. To clear this cache of your shell you need to run hash -r or simply start a new shell.

Note: See TracTickets for help on using tickets.