It might be getting a non-Cygwin version from somewhere such as c:/Program Files.Īnd if you're still having problems, check $PATH that all directories starting with /cygdrive/ came after all directories without. Nor was Perl or Python, which I put right.Īnyone else with this problem under Cygwin, I'd recommend going through Category view in select Packages and checking what you want is installed.
#Vim devicnos after source vimr install#
But when I went back to the Cygwin Install Packages page I found vim wasn't installed. I've been using vi on and off since I learned it 35 years ago so just expected it to be there like it is in most distros. I'd just brown away away Cygwin and reinstalled from scratch - I was trying to resolve problems with some Python scripts which worked months ago but now wouldn't. This thread was the most promising result from a Google search, so I'll add my solution. I got this error running vi under Cygwin. If someone told you to install Vim as a prerequisite for learning some programming language, then that someone should help you install, configure, and learn it. You should a) give up on Vim, b) get a regular text editor or IDE so that you can focus on learning C. Isn't it Albert Einstein who had something to say about doing the same thing over and over and expecting a different result? If it does, stay away from C:\Program Files\Vim.Īgain, C:\Program Files\Vim is off-limits. A thorough wipeout followed by a clean install may help. This is either a sign that you messed up Vim's runtime or that the installation didn't work as it should. If you did and you are still lost, then use the plugin's issue tracker. You are expected to read those documents carefully and follow them.
#Vim devicnos after source vimr windows#
The repo's README.md points to this document specifically targeted at Windows users and to a general FAQ. That is where you are supposed to install plugins. %userprofile%\vimfiles\vimrc <- this is YOUR vimrc The right place for customisation is in your %userprofile%, which is Window's equivalent of the $HOME or ~ you may find in tutorials): %userprofile%\vimfiles\ <- this is YOUR runtime directory, where You literally have no business doing anything there. The only "proper" _vimrc is the one you build yourself, as your needs and knowledge evolve.Ĭ:\Program Files\Vim is off-limits. Please help, because I'm going to foam from my mouth soon with this Vim. Then I've surrendered and went here to seak for a help/advice/mercy. Again, the reinstalled Vim didn't work properly because of the same error 1187 although it showed the contains of _vimrc file, but for reading only. But once again, the installation of Vundle informed me that "vimfiles\bundle" folder was not empty, so "suck, my dear". The answer was: "this directory is not empty etc."Īfter another session of crying I accepted the challenge and deleted (de-installed) Vim, downloaded it as from the very beginning, repeated all the aforementioned actions.
I thought that it might be the second repository, which led me to the mistake, so I recreated vimfiles\bundle folder, but for this time I used the first repository with shortening my directory as in the second repository command (~/vimfiles/bundle/Vundle.vim). I've cried a bit, but then gathered myself and decided to delete the whole "vimfiles" folder in hope to make it back to the previous step.
The Vim window opened without any functionality, empty, with only two lines on the bottom containing, I guess, the file size info. And as soon as I've tried to open _vimrc via Vim (or gVim), it showed a warning with Error E1187: failed to source defaults.vim.
The next step instructed to edit the _vimrc file, to add some strings about Vundle into it. After the process was finished, I've checked the vimfiles\bundle folder, it appeared to be empty, but never mind, I did as I was told to. It actually worked (I thought), black plate of CMD got filled with multiple white letters indicating the downloading process. Okay, I googled for it more and found another tutorial with CMD instruction, which advised to insert a "git clone ~/vimfiles/bundle/Vundle.vim" command. Common CMD told me GTFO, but Git CMD reacted to the command, though again refusing to satisfy me, as there were "too many arguments". As in tutorial, I've made in C:\Program Files\Vim a "vimfiles" directory with "bundle" folder and followed the instruction to insert in CMD "git clone C:\Program Files\Vim\vimfiles\bundle". Vim started working successfully (at least, it opened without errors, showed all the functionality and let me edit the _vimrc file (I mean, before looking for a proper one in the web)). I installed Vim (32-bit) from here ( ), adjusted it (added to path, edited enviromental variables and so on as in tutorials), found a proper _vimrc file. I'm absolutely new in C and Vim (now learning), started from Python, but now turned to C for educational reasons, along with which I had to learn the Vim (the point is, it wasn't my choice).
0 kommentar(er)
