On Sunday, February 17, 2013 4:01:10 PM UTC+13, ping wrote: > typically they are sth like: > > asciidoctips.txt~ > .asciidoctips.txt.un~ Those are backup files. The file you are editing is renamed to something like this before the new version is written. > .pers-notes.txt.swh > .pers-notes.txt.swi > .pers-notes.txt.swj > .pers-notes.txt.swk > .pers-notes.txt.swl > .pers-notes.txt.swm > .pers-notes.txt.swn > .pers-notes.txt.swo > .tech-tips2.txt.swp
Those are all swap files. The fact that there are many for .pers-notes.txt implies that vim has been killed or crashed a lot. Normally, swap files are deleted when vim exits cleanly. > just want to confirm, to make sure there is not a single additonal file > generated by vim under all circumstances, are following settings sufficient? > > set nobackup > set noudf In principle, you'd want set noswf as well, but I think your approach is ... well, would "foolhardy" be acceptable? Perhaps "risky" is better. These backup and swap files protect against losing your files. One doesn't need them often, but I've been very glad on several occasions. Undo files are off by default. You shouldn't be getting stray swap files, it's much preferable to work out why vim is dying and fix it. Note that after vim does die, on the next restart vim warns you about the problem but is reluctant to delete the file, you may have to manually delete it. Backup files are IMO better tamed using the backupdir option to put them in a central place. Regards, John Little -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
