E138 Can T Write Viminfo File
When you run sudo vim you start vim as root. That means that it is the viminfo file in /root that is the problem. You should do rm /root/.viminf. To make sure of this, run sudo vim and execute this command::!echo $HOME. This will show you that your home directory is /root. I would recommend that you do not run vim as root, but rather use sudoedit. This is a more secure solution as the editor is not running as root.
You never know what a plugin might do. Additionally it allows you to use your own settings and plugins in vim and not the ones in roots vimrc. Sudoedit is the same as running sudo -e. Sudoedit works by making a temporary copy of the file that is owned by the invoking user (you). When you finish editing, the changes are written to the actual file and the temporary file is deleted.
2012 volvo c30 manual. View and Download Volvo C30 2012 owner's manual online. C30 2012 Automobile pdf manual download. VOLVO C30 Owner's manual Web Edition. Welcome to the world-wide family of Volvo owners. We trust that you will enjoy many years of safe driving in your Volvo. Volvo C30 Owners Manual. Below are Owners Instruction Manuals in PDF file format for the S40 V40 Series. Volvo C30 2012 Owners Manual. Volvo C30 2012 Quick Guide. Research the 2012 Volvo C30 online at cars.com. You'll find local deals, specs, images, videos, consumer and expert reviews, features, trims, and articles for every.
Give More Feedback
See More On Stackoverflow
I saw this Error E138 while editing some file with VI Editor. The error description is like this. E138: Can't write viminfo file /root/.viminfo!Hit ENTER or type. E138: Can't write viminfo file. The error occurs within vi and not my program. There is no overflow in sprintf because everyting has a null terminating character placed on the end. The editor preference comes as a default of vi but is manipulated by the user through the config file. E212: Can't Open File For Writing section labeled # History of marks within files (newest to oldest). Editing viminfo files, they show up in the proper colors.
As a general rule of thumb: Do not run things as root if it is not necessary. Hope this helps you!