It's awesome that jedit keeps many backup copies of a file, however I feel there's a fundamental flaw with the backup filename convention that jedit uses.
I, for example, have nominated for Jedit to keep a backup of up to 1000 copies of a file. This is great! However why does jedit create backup files like this:
where a.txt1 is the earliest and a.txt3 is the latest backup of a.txt
If say I need to restore the last successful edit of a file I need to find the highest number jedit has allocated to that particular file. This is easy if I was working on one file in one directory. But when I've been working on 1000 files in one directory it becomes really unwieldy. Like I have to go through every single file, work out the highest number for each file which is really time-consuming and therefore annoying, especially seeing 11 is less than 2 as far as the filesystem is concerned.
I suggest a basic change to the file-naming strategy:
If jedit makes a backup of a.txt on a save and it hasn't backed up a.txt before then it simply backs it up as a.txt. The next time jedit makes a backup of the same file it should rename the already backed up a.txt to a.txt1 and then save the backup of a.txt as a.txt. The next time I save a.txt it should rename the last backup of a.txt to a.txt2 before backing up as a.txt again.
That way if I need to "get back" the last copy of everything I've edited in a directory I can simply copy *.txt or whatever the normal extension is out of the backup directory and, viola, I have every latest copy of every file that jedit managed to backup successfully.
ps: wicked editor guys - I've been coding with it for years - you won't catch me using an IDE no sir.