Found out why vim/vundle didn't work
I sent an earlier message to the list (or possibly to the vim list) about my problems in getting the vundle distro to work under the vim text editor. I am glad to report that the problem is solved, and this is what I found: This is a cygwin problem, although not necessarily a bug; more like a PEBCAK problem in the package selection stage, as there are 3 vim packages to choose from. The vim command is a different vim than the vi command. Both are vim, but come from different vim packages. In Linux and other *nix systems, vi is symbolically linked to vim, but not in this case. These are different copies of vim, and both look in different places for the .*rc file. I found that vi looks first in ~/.virc and second in ~/.vim/vimrc. When you install vundle. the second place is a directory, causing vi to choke. Even when that is corrected, it doesn't know how to handle the Bundle command, and you get a wild flurry of error messages. vim, however, looks first in ~/.vimrc which exists, and in turn sources files under ~/.vim/vimrc. It waits a few moments, then opens your file. This is consistent with my experience with vim/vundle under other OS'es. So, for me it was just a matter of logging in with my Administrator account, then moving vi to _vi; then agreeing with custom, linking vim symbolically to vi. Paul King -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
VIM Vundle not working under Cygwin64
Hello I have tried to get vim's vundle package to work under Cygwin64, and it appears as though vim doesn't understand most of the package. Vundle works under 32-bit Cygwin, but something in the way the 64-bit version was compiled looks in the wrong place for vimrc. The 64-bit version (sorry I forget the version number (I uninstalled it), but it is the one under the very latest 64-bit distro) thinks that vimrc resides under ~/.vim/vimrc (a directory in my case). It does not look at my ~/.vimrc file at all. I got this info using :version When I force it to do so (vim -u ~/.vimrc filename), I get a ton of errors as it does not seem to understand most of the Vundle commands. That could also be from the fact that it might be an older version of vim, but since I uninstalled it, I can't be sure. I would like the vundle package to work the way it does under any other *NIX system I use, including Cygwin32. Is there a Cygwin-specific source package I can download or is there a way someone could re-compile a more recent binary so that it understands things like a standard location for ~/.vimrc and vundle commands? Thanks Paul -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problems in configuring Perl on Cygwin-64
I have run into unusual problems in configuring Perl from the time I began using perl on my new Windows 7 installation (which was two days ago). I wanted to introduce libraries into the Perl distro, and my customary way of doing this is to invoke: perl -MCPAN -e shell which brings up the Perl config shell. Usually, when I do this for the first time on a new installation, it asks me to configure stuff, and I chose yes (as I always do) to auto-configure. It ended with an error (sorry I forget what the error was), which has never happened before. Would anyone know how to re-run this config (which seemed to go on its own) so that I can reproduce the error? Paul King -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: getting the right setup.bz2
If you just want to download all the packages to a local directory and install from there, you don't need a setup.ini (setup.bz2) file. THat's good news. However, it seems to lead to the packages being lumped under Misc as I said earlier. This would seem to make deselection by groups of packages impossible, so is there a way to bring back the hierarchy in a way that finds the files as well? Paul King Actually, I found a way to coax group selection/deselection in a certain way, and that was using the search feature in package selection. I still end up with a lot more stuff than I intended in the distro. It installed overnight and it is has just stopped installing after 7 hours or so (mostly due to postinstall, I'm guessing). Paul -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Fwd: getting the right setup.bz2
I downloaded a Cygwin repository using wget -r -T 30 -t 20 -nc , and I seem to be having trouble with setup.bz2. When I use it, I get the packages listed, but the top level tree in the package selection window (in setup) says no packages found. The packages are listed beneath it anyway. Without setup.bz2, I don't get the error, but everything is listed under Misc. Do I need to generate my own setup.bz2 for what I downloaded, and how do I do this? Is there a guide specifying what setup is Note that I already have a working Cygwin installation. I wanted to make another installation on another computer, and going via the normal setup.exe route thorough an FTP site led to too many stalled/aborted downloads. Paul King -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple