On most machines I work on, most files that I use are not part of any version control system. For either fixing mistakes, or seeing past changes, I make dated backups of files I'm working on.
NPP does keep changed files, but that wouldn't help someone else working on it, or me when I'm on a different machine. Especially with system files, I may just be on the console of the machine using vi, so it'd be impossible to see my old revisions without these local dated backups.
I usually accomplish this by logging in via SSH, and copying the file manually before editing.
I'd guess that others would want to be able to use the format of their choice. I would like the format to be YYYYMMDD_r , where r is just the revision in case I have multiple changes that day.
In lieu of dates, just a "Make Duplicate" option would work, then requiring the file to be renamed to the date later. I'd really appreciate the dated backup. Maybe it'd encourage more users to keep backups while they're working. I've seen too many new people just change files without having any backups. I do have NPP saving backups locally on my desktop, but a lot of small changes can really make a mess to read through on servers. Just having the intentionally created dated backups on the servers works better.
The photo is a real example. That server had it's IP changed twice this year, thanks to some nonsense from the provider changing IP blocks. I can read or diff them at any time, to see what we changed from.
I might be able to write this change, but I don't know how you guys are about accepting 3rd party changes. I'd rather stay current with your version, than to fork my own.
Feature Request: Dated backup files.
On most machines I work on, most files that I use are not part of any version control system. For either fixing mistakes, or seeing past changes, I make dated backups of files I'm working on.
NPP does keep changed files, but that wouldn't help someone else working on it, or me when I'm on a different machine. Especially with system files, I may just be on the console of the machine using vi, so it'd be impossible to see my old revisions without these local dated backups.
I usually accomplish this by logging in via SSH, and copying the file manually before editing.
I'd guess that others would want to be able to use the format of their choice. I would like the format to be YYYYMMDD_r , where r is just the revision in case I have multiple changes that day.
In lieu of dates, just a "Make Duplicate" option would work, then requiring the file to be renamed to the date later. I'd really appreciate the dated backup. Maybe it'd encourage more users to keep backups while they're working. I've seen too many new people just change files without having any backups. I do have NPP saving backups locally on my desktop, but a lot of small changes can really make a mess to read through on servers. Just having the intentionally created dated backups on the servers works better.
The photo is a real example. That server had it's IP changed twice this year, thanks to some nonsense from the provider changing IP blocks. I can read or diff them at any time, to see what we changed from.
I might be able to write this change, but I don't know how you guys are about accepting 3rd party changes. I'd rather stay current with your version, than to fork my own.