Vim backup file name

Latest commit. Git stats commits. Failed to load latest commit information. View code. The writebackupToAdjacentDir. This helps where the backups cannot be placed into the same directory. The writebackupAutomator. It can be your safety net when you forget to make a backup. If the last backup is identical with the current buffer contents, no redundant backup is written.

With [! About Write backups of current file with date file extension. Resources Readme. Releases 1 tags. Packages 0 No packages published. You signed in with another tab or window. Reload to refresh your session. Last active Dec 29, Code Revisions 2 Stars 32 Forks 3.

Embed What would you like to do? Embed Embed this gist in your website. Share Copy sharable link for this gist. Learn more about clone URLs. Download ZIP. Auto-backup your configuration files with Vim — First published in fullweb. Auto-backup your configuration files with Vim Not using versioning on your configuration files and editing them with Vim?

Copy link. Thank you so much, this saves me a lot of time. Great tip, working out of the box!! This seems to work for a backup each and every time the file has changed and it does so with a correctly dated and absolutely unique filename in the trash directory. A trash dumping utility would have to go by the file attributes anyway, right? So here we go:. The above says create an new autocmd that will be executed when writing a file or buffer is finished. The bang i.

The command itself is nothing more than a few BASH commands all on the same line. I could have just as easily used a bash script to take care of this. It would have been much neater to look at but not as copyable and self contained. The script would have looked like this:. If I were to decide to put this script in my command path and use it, my autocmd line would have looked like this:. With help from others I got it tested and working for gvim 7.

I assume for 6. Vim Tips Wiki Explore. Main Page All Pages Community.