The case where you want to compile different versions of Vim with not only different configuration options but even different changes to the sources is not covered by the present tip, and neither is the case when your changes could conflict with Bram's (the changes I have consist of added sections in out-of-the-way parts of Makefile and feature.h plus Bill McCarthy's extra float functions).Īlso, check that your "nonstandard" patches (if any) are mentioned in src/version. You do this by editing the sources in the src directory. The -e command-line switch is necessary so that make won't override our SHADOWDIR names with the default which is just shadow Apply your local changes and commit them (date & SHADOWDIR='shadow-tiny' make -e shadow) 2>&1 |tee -a. (date & SHADOWDIR='shadow-huge' make -e shadow) 2>&1 |tee -a. hgignore (after applying the above patch) will see them. Some other commands should also have '' appended, which means. When you define functions in vimrc, use 'function'. However I get a lot of errors (E174) saying command already exists for each line in my vimrc. vimrc source I did this and it seems to work. We create them with names starting with shadow- so. If you find yourself always re :so ing your vimrc after you changed it, have the following autocmd in your vimrc: autocmd bufwritepost. If you want to compile more than one version of Vim, create shadow directories to avoid conflicts between them. This step is unnecessary if you have neither additional help files nor additional Vim versions and you don't add a cscope database inside the Vim source tree.Ĭopy the following patch and apply it with patch -p1 &1 |tee -a. It is found at the top level of your repository. No need to add anything after the equal sign, this extension comes packed with Mercurial (but disabled by default) hg/hgrc file in your repository (it was created by the clone process, with Bram's repository as the default remote source): hg-vim.logĬomplex case: You have local changes and/or compile several Vim versions Enable the fetch extension Īdd the following to the. In this case, all you need to check for (and, if necessary, get) any changes to the Vim source is:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |