The configuration we have seen during this chapter might take some time to set up manually. But once everything is configured, we can create a script that will restore the vim configuration instantly. For this, we paste all the commands issued until now into a bash script, which can be run to bring vim to the exact same configuration. All that is missing from this script is the vim configuration file from the home folder, which we can also restores for technical here Doc's just that get redirect the output to vim config to the vim configuration file, and use your doc as input delimited by and the file. Here dogs is a common technique for manipulating large chunks of text inside bash scripts. Basically, it treats a section of a code like a separate file, in our case, everything after the cat and until the end of file.

With this script, we can restore all the vim configurations we have done and we can also run it on any different color. pewter we work on, so that we get our vim set up in no time. You can find the full script on the GitHub repository together with all the Course Resources. If you haven't already cloned it, check the link in the description. We have reached the end of the vim chapter. A friend of mine used to say, I've been using vim for two years now, mostly because I can't figure out how to exit it.

This is a joke. Of course, lots of people find him hard to use because of its exotic keyboard shortcuts and commands. But once you get the hang of it, it helps you become very productive. This doesn't mean you should just go and replace your either with vim now, but for most of the common tasks that need to be completed from the terminal, vim is an ultra fast option that gets the job done. We hope you have enjoyed this video and see you in the next one.