Re: Undo Levels Reset
J. Erik Heinz wrote: Hi, Dimitar [EMAIL PROTECTED] words on 24.03.2007 - 10:08 (+0100 Zulu-Time): * Vigil [EMAIL PROTECTED] [070323 22:20]: When a file is saved with :w, any changes in the undo history are lost and I can't undo things to get back to a state before I saved the file. It happens sometimes to me too. However I cannot reproduce it. At the moment my vim has this behaviour as well. And this occurs when I start vim without any configuration files ( I moved .vimrc and .vim, so that vim dont source it anymore by default) Especually the .vim is important. At the moment my .vim holds very little configuration files, and as it seems not the configuration that makes the undo work nicly ( or better remember the older undo's after :w ) From my point of view, it must be a general configuration setting that is missing. Cheers -- Erik Without a .vimrc, Vim will start in 'compatible' mode, unless you include the -N command-line switch. This means that a second undo is actually a redo: u u is a do-nothing operation. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 136. You decide to stay in a low-paying job teaching just for the free Internet access.
Re: Undo Levels Reset
* Vigil [EMAIL PROTECTED] [070323 22:20]: When a file is saved with :w, any changes in the undo history are lost and I can't undo things to get back to a state before I saved the file. It happens sometimes to me too. However I cannot reproduce it. Yours, Dimitar How can I prevent the history being lost? -- .
Re: Undo Levels Reset
Hi, Dimitar [EMAIL PROTECTED] words on 24.03.2007 - 10:08 (+0100 Zulu-Time): * Vigil [EMAIL PROTECTED] [070323 22:20]: When a file is saved with :w, any changes in the undo history are lost and I can't undo things to get back to a state before I saved the file. It happens sometimes to me too. However I cannot reproduce it. At the moment my vim has this behaviour as well. And this occurs when I start vim without any configuration files ( I moved .vimrc and .vim, so that vim dont source it anymore by default) Especually the .vim is important. At the moment my .vim holds very little configuration files, and as it seems not the configuration that makes the undo work nicly ( or better remember the older undo's after :w ) From my point of view, it must be a general configuration setting that is missing. Cheers -- Erik -- J. Erik Heinz Keyboard-samuraing in process :: All non-mailinglist mail to this emailadress will be deleted. Xing: https://www.xing.com/profile/JErik_Heinz Blog: http://jerik.blogspot.com
Undo Levels Reset
When a file is saved with :w, any changes in the undo history are lost and I can't undo things to get back to a state before I saved the file. How can I prevent the history being lost? -- .
Re: Undo Levels Reset
Vigil wrote: When a file is saved with :w, any changes in the undo history are lost and I can't undo things to get back to a state before I saved the file. How can I prevent the history being lost? Huh? When I save a file, undo levels are kept. Using u then undoes, but marks the file as modified. Using Ctrl-R redoes, and the 'modified' flag will disappear when the file-in-memory is identical to the file-on-disk. The undo history is only lost when I close Vim with :qa Best regards, Tony. -- You can't have everything. Where would you put it? -- Steven Wright
Re: Undo Levels Reset
A.J.Mechelynck wrote: When I save a file, undo levels are kept. Using u then undoes, but marks the file as modified. Using Ctrl-R redoes, and the 'modified' flag will disappear when the file-in-memory is identical to the file-on-disk. This is my experience as well. Undo levels are only lost when I close Vim, when I reopen the file with :e, or when Vim alerts me that the file has been changed and reloads it. The latter can be dangerous if you're not careful, and I'd appreciate any tips to work around it. Tobia
Re: Undo Levels Reset
Hmm. My bad, I guess. I must have had some weird settings at the time. Sorry, list! A.J.Mechelynck wrote: When I save a file, undo levels are kept. Using u then undoes, but marks the file as modified. Using Ctrl-R redoes, and the 'modified' flag will disappear when the file-in-memory is identical to the file-on-disk. -- .