Home > Cannot Write > Cannot Write Viminfo File /home/work/.viminfo

Cannot Write Viminfo File /home/work/.viminfo

share|improve this answer answered Sep 24 '15 at 11:28 steeldriver 32.4k44477 ,thank you so much –igx Sep 24 '15 at 12:05 add a comment| up vote 0 down vote Adams Aug 29, 2004 File - partially Read-Only and partially Write-Only karthikbalaguru, Mar 16, 2008, in forum: Embedded Replies: 8 Views: 498 Robert Adsett Mar 18, 2008 Re: can't load REAL Left by muhammad shamseer on Mar 05, 2009 10:20 PM # re: Error E138 with VI Editor - E138: Can't write viminfo file /root/.viminfo! I just started my first real job, and have been asked to organize the office party. this contact form

also I look for temp file like "~/.viminf*" but there nothing like this. When you get error "E138: Can't write viminfo file" check that no old temp files were left behind (e.g. ~/.viminf*) and that you can write in the directory of the .viminfo jbclem, Jul 9, 2003, in forum: Asus Replies: 1 Views: 944 EC Jul 10, 2003 How do you format an ARM axf file to write directly to flash Chris, Sep 7, I was also facing the same issue!!! 3:09 AM Namit said... http://unix.stackexchange.com/questions/134500/vim-error-e138-cant-write-viminfo-file-home-viminfo

Comments (17) | Share I saw this Error E138 while editing some file with VI Editor. The error description is like this. I think i removed it while trying to fix things.

Ooo yes worked like a dream :) 8:36 PM Anonymous said... Hit ENTER or type command to continue Does anyone know what is wrong?? Draw a hollow square of # with given width Is the result of the general election final on 8th of Nov, 2016? share|improve this answer answered Nov 12 '15 at 2:16 Partha S Ghosh 1 1 That seems a bit farfetched: do you have any evidence for that? –jasonwryan Nov 12 '15

more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Check your quota, you may not be able to write to ~/ Left by PC on Jun 22, 2010 1:42 PM # re: Error E138 with VI Editor - E138: Can't sudoedit works by making a temporary copy of the file that is owned by the invoking user (you). Make sure you have show hidden files enabled. –Zach Sep 1 '14 at 13:45 The file is not shown in the filesystem in the GUI (probably, since it is

Why did the Bordens share their wife in the movie The Prestige? How do you delete these files? Join them; it only takes a minute: Sign up E138: Can't write viminfo file $HOME/.viminfo [closed] up vote 6 down vote favorite 1 I am using opensuse for my production environment. Why is looping over find's output bad practice?

Find all posts by ynilesh #3 08-04-2008 MLT1988 Registered User Join Date: Jul 2008 Last Activity: 4 August 2008, 6:12 PM EDT Posts: 2 Thanks: 0 Thanked 0 http://askubuntu.com/questions/677852/trying-to-change-file-in-recovery-mode-and-getting-e138-cant-write-viminfo-fil Left by Sandip Sinha on Mar 02, 2010 10:10 PM # re: Error E138 with VI Editor - E138: Can't write viminfo file /root/.viminfo! Worked. Removing ~/.viminfo did not fix the error.

All Rights Reserved. weblink I needed a local variable and decided to name it HOME, so I entered the line HOME=2.154. move to directory that was no directory Underbrace under nested square roots I changed one method signature and broke 25,000 other classes. Removing the .viminfo.tmp file worked like a dream for me. 11:13 PM Pauli said...

root recovery-mode ubuntu-core share|improve this question edited Sep 24 '15 at 11:43 TRiG 1,16711230 asked Sep 24 '15 at 11:02 igx 1084 Did you remember to remount the filesystem sudoedit is the same as running sudo -e. more hot questions lang-sh about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science Other navigate here You can also move it to a different place if you think it may contain some important things that you don't want to lose.

rm -rf ~/.viminf* # Remove them. Thanks for the solution. Ok I restored my /root/* from tape and now everything seems to be working.sof123 are you still needing help?

This will show you that your home directory is /root.

Thanks for the easy to follow advice, this helped me solve this problem too! 7:59 PM aravindous said... Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... How to make my logo color look the same in Web & Print? Vim wants to write that file.

more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science Great help! asked 2 years ago viewed 18872 times active 1 month ago Related 53Becoming root from inside Vim5Problem with vim when logged in as root0Root user can't do everything?6Remove all Vim undo his comment is here Can anybody tell why this .vimif* file get generated?and is this a log file which takes the commands we type in shell?

When [!] is used, the old information is not read first, only the internal info is written. Yes. asked 1 year ago viewed 1297 times active 1 year ago Related 7How to boot to root shell when GRUB recovery menu fails to load a shell?3Why there is no password If [!] is given, then any information that is already set (registers, marks, etc.) will be overwritten. {not in Vi} *:wv* *:wviminfo* *E137* *E138* *E574*:wv[iminfo][!] [file] Write to viminfo file [file]

asked 3 years ago viewed 16878 times active 3 years ago Upcoming Events 2016 Community Moderator Election ends Nov 22 Related 213How do I send a file as an email attachment I am looking through my backups now but not sure how to restore ~ Left by Jason Landstrom on Sep 03, 2009 11:08 AM # re: Error E138 with VI Editor What is the output of ls -la .vininf*? –darnir Jun 4 '14 at 16:42 add a comment| 6 Answers 6 active oldest votes up vote 14 down vote accepted When you If 'viminfo' is empty, marks for up to 100 files will be written.

I have the same error.Thank you Left by sof123 on Aug 27, 2009 10:01 AM # re: Error E138 with VI Editor - E138: Can't write viminfo file /root/.viminfo! Hot Network Questions How can I ask about the "winner" of an ongoing match? Left by shrikant on Mar 19, 2013 8:42 AM Your comment: Title: *So what is this about? source here share|improve this answer answered Sep 24 '15 at 11:16 kashish 572619 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using

I'm getting this response when using vim to edit my C++ programs: E138: Can't write viminfofile /home/mlt1988/.viminfo! About Us We're a forum dedicated to providing support and advice for motherboards, chipsets and drivers from all manufacturers. file as well, but all attempts in vain.Some message if u see again and again, it is real frustrating.Finally, today i decided to get rid of this message once and for

Back to Top