On Fri, April 20, 2007 11:29 am, Marv Boyes wrote:
> 1- After removing every trace of Ubuntu's default-installed vim, I
> installed the following from repositories:
>
> vim-common
> vim-full
> vim-gui-common
>
> That gave me vim with the GNOME2 interface. The command 'gvim' runs
> Vim 7.0.164 with a GUI. The command 'vim' returns the error
> "/usr/local/bin/vim: No such file or directory". So, apparently,
> text-mode vim vanished for some reason, or my paths got screwed up.
> (Please pardon the undoubtedly inaccurate terminology.)
Check your ~/.bashrc and ~/.bash_profile files to see if you have a vim
alias pointing at that location. Also, your EDITOR system variable
might be pointing at that explicit location. You can check that
variable using the following command:
$ echo $EDITOR
If your editor is pointing at /usr/local/bin/vim, then you may want to
just change it to "vim".
> 2- After removing every trace of Vim as installed above, I ran AAP
> with "--enable-gui=gnome2" in my config.arg. I got Vim 7.0.224 in
> text-mode, but the GUI is reported as having _not_ been enabled at
> compile time.
Ok, first, did you run the "build-dep" commands that I referenced in my
previous e-mail message? Please note that I didn't ask you to run
"apt-get install"; you should be running "apt-get build-dep" in order to
install all of the gui dependencies that Vim requires.
Next, you don't have to uninstall the Ubuntu version of Vim in order to
install the AAP version. It's my understanding that AAP installs the
vim folder tree under /usr/local, not /usr (like the Ubuntu package).
Not uninstalling the Ubuntu packages if they're already there will
probably save you time and make troubleshooting easier.
Now, if you installed the gui dependencies and are still having
problems, then we need to find someone who's more familiar with AAP. If
I were install vim from source the old fashioned-way, I would do the
following:
$ cd /arbitrary/vim/build/dir
$ ./configure --enable-gui=gnome2 2>&1 | tee ./config.custom
(the previous command configures vim and sends STDOUT and STDERR to
the config.custom file. Tee is used to also send all output to the
terminal)
(lots of output)
$ grep -i error ./config.custom
$ grep -i exception ./config.custom
$ grep -i gui ./config.custom
$ grep -i gnome ./config.custom
(the previous three commands tell you if there were any problems
with the config. The "gui" search is especially important)
I'm assuming you can do some similar troubleshooting using AAP, but I'm
not familiar with that process. Does anyone else know how you can do
this with AAP?
> Again, I'm sorry if I'm missing something extremely basic; it's just
> that nothing I'm trying is working.
No reason to apologize, a lot of people have had problems compiling vim
with gui support in the past. Also, there aren't really any trolls on
this list, so you don't have to walk on egg shells :)
HTH!
Tom Purl
