Vim error 1187 (cannot source the defaults.vim file) after installing Vundle

Question

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). The system is Windows 10. Here is the problem:

1. I installed Vim (32-bit) from here (https://github.com/vim/vim-win32-installer/releases), adjusted it (added to path, edited enviromental variables and so on as in tutorials), found a proper _vimrc file. 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)).

2. The next step was to install a Vundle. 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 https://github.com/VundleVim/Vundle.vim.git C:\Program Files\Vim\vimfiles\bundle". Common CMD told me GTFO, but Git CMD reacted to the command, though again refusing to satisfy me, as there were "too many arguments".

3. Okay, I googled for it more and found another tutorial with CMD instruction, which advised to insert a "git clone https://github.com/VundleVim/Vundle.vim.git ~/vimfiles/bundle/Vundle.vim" command. It actually worked (I thought), black plate of CMD got filled with multiple white letters indicating the downloading process. 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.

4. The next step instructed to edit the _vimrc file, to add some strings about Vundle into it. 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 Vim window opened without any functionality, empty, with only two lines on the bottom containing, I guess, the file size info.

5. 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. It didn't work. 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). The answer was: "this directory is not empty etc."

6. After 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. But once again, the installation of Vundle informed me that "vimfiles\bundle" folder was not empty, so "suck, my dear". 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.

7. Then I've surrendered and went here to seak for a help/advice/mercy. Please help, because I'm going to foam from my mouth soon with this Vim.

Answer 1

On Cygwin I solved this by installing vim package which was missing:

Answer 2

This is still a problem in Cygwin64 releases.

Since this is one of the highest posts on Cygwin64 VI with the error "Cannot source the defaults.vim file", I thought to post this simple, quick fix.

Touch .exrc in your home (~) directory (cygwin64 home, not windows). Problem goes away. I found the answer last year on a Redhat forum when it cropped up as an issue years ago. Note this is an .exrc and not .virc or .vimrc file as one answer here gives.

Answer 3

I had this issue after building from source. I created .vimrc file in my ~ directory and the issue was resolved.

Answer 4

Here's the short answer:

1. make a file %userprofile%\vimfiles\vimrc
2. try starting gVim again, and see if the error goes away

Note that in more modern PowerShell syntax, the environment variable punctuation is a little different. Here's how it looks on my machine:

cat $env:userprofile\vimfiles\vimrc

" this is a vimrc file with nothing but a comment in it

Answer 5

I got this error running vi under Cygwin. This thread was the most promising result from a Google search, so I'll add my solution. 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.

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. But when I went back to the Cygwin Install Packages page I found vim wasn't installed. Nor was Perl or Python, which I put right.

Anyone else with this problem under Cygwin, I'd recommend going through Category view in select Packages and checking what you want is installed. It might be getting a non-Cygwin version from somewhere such as c:/Program Files.

And if you're still having problems, check $PATH that all directories starting with /cygdrive/ came after all directories without. (Since previously running my Python scripts I'd reinstalled Windows Python, which may have messed up cygwin's $PATH.)

And if you're not using Cygwin, check your $PATH anyway, and/or use the type command to check what executable you're actually being given.

Answer 6

1. You are not supposed to "find" a _vimrc. The only "proper" _vimrc is the one you build yourself, as your needs and knowledge evolve.

2. C:\Program Files\Vim is off-limits. You literally have no business doing anything there. 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
                                     all your Vim customisation should happen
   %userprofile%\vimfiles\vimrc  <-- this is YOUR vimrc
   

   That is where you are supposed to install plugins.

3. The repo's README.md points to this document specifically targeted at Windows users and to a general FAQ. You are expected to read those documents carefully and follow them. If you did and you are still lost, then use the plugin's issue tracker.

4. This is either a sign that you messed up Vim's runtime or that the installation didn't work as it should. A thorough wipeout followed by a clean install may help. If it does, stay away from C:\Program Files\Vim.

5. Again, C:\Program Files\Vim is off-limits. You don't delete stuff. You don't add stuff. You don't change stuff. You leave it be.

6. Isn't it Albert Einstein who had something to say about doing the same thing over and over and expecting a different result?

7. You are wasting your time. You should a) give up on Vim, b) get a regular text editor or IDE so that you can focus on learning C.

---

(the point is, it wasn't my choice)

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.

Your failure is on them.