On Tuesday, May 15, 2012 12:24:21 PM UTC-5, Chris Jones wrote: > On Tue, May 15, 2012 at 11:23:57AM EDT, Ben Fritz wrote: > > > Since the error only occurs if 'backup' and 'writebackup' are both > > off, maybe we could only do the "dry run" conversion in this > > situation? I.e., if either 'backup' or 'writebackup' are set, do what > > Vim has always done; but if neither are set, do the extra check first. > > We could even put a nice notice in :help 'writebackup' saying "if this > > option is off, writing the file will take longer due to extra safety > > checks" to discourage turning it off in the first place. > > So you would penalize those of us who turned off this backup/writebackup > bloat..? >
>From Christian's test data, it looked like the slow-down was on the order of a >few seconds for a write of a big file. I think that would be a small price to >pay to know that the entire content of your file isn't going to be lost >because Vim decided it could not modify them. I don't consider it a penalty. I >consider it giving users some of the security of 'writebackup' even if they >don't have it turned on. > Or would you force us to reinstate it so as not to be penalized..? > > Aha... you turned off backup and writebackup.. you wicked little > so-and-so.. You seriously thought you were going get away with it..? > It's risky, but it's also a valid use scenario, so that's why I want to see the file contents protected against being cleared for no good reason, even if the option is turned off. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
