The following command sources my vimrc file as soon as I modify it. Having a minimal vimrc file makes it more manageable and it takes you less time to figure out the setting when you revisit it after a few years. So, your vimrc file does *not* need the following line. In the example above, errrorbells (a beep in case of an error) is off by default. If you look at the help of a setting and it defaults to what you need, you don’t have to have it in your vimrc file unless some plugin is overriding your defaults. I realized recently that my vimrc file contained some obvious defaults. Reconstructing your vimrc file from scratch is painful and should not be done. vimrc falls squarely in that category as well. If you are a software developer, we have reached the age where code, infrastructure, configuration should be treated as code and regularly checked in. cd ~ git clone echo so ~/config/vimrc > ~/vimrc Configuration is code.Īs noted above, I check-in my vimrc file to github. I always sync the file to a folder such as ~/config and then I modify the default vimrc file and source the file that I synced. I don’t use the vimrc in the default location. So, even if I don’t have access to, I usually do have my vimrc available to me through the backup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |