What steps will reproduce the problem?
1. Get conque 2.3.vmb
2. Install Conque as described by editing the .vmb, and executing so %.
3. Restart vim.
What is the expected output? What do you see instead?
I expect Conque to be completely installed into ~/.vim/. However, I have now
seen this fail on two completely different Linux installs: CentOS 5.3 with vim
7.0.237 and Ubuntu 10.04 with vim 7.2.330.
On the CentOS set-up it was quite clear something had gone wrong with the
install as several of the files installed into ~/.vim/ had corrupt file names
(special characters were append at the end). On the Ubuntu system it was less
obvious that the install was the issue. After manually fixing the file names on
CentOS, both systems remained non-functional, this manifested in the ConqueTerm
command and many g: variables being undefined (I got the the g: errors by
manually source'ing ~/.vim/autoload/conque_term.vim and invoking
conque_term#open("bash")).
Eventually I got things working by downloading the .tar.gz and manually
extracting it. It looks as though several extra files were installed,
particularly plugin/conque_term.vim.
I would suggest the install guide for Conque make it clear that vimball
installation can be problematic (I guess particularly with older systems) and
perhaps provide instructions on how to extract .tar.gz etc.
Original issue reported on code.google.com by ja...@maxeler.com on 29 Oct 2012 at 4:44
Original issue reported on code.google.com by
ja...@maxeler.comon 29 Oct 2012 at 4:44