Track Changes: For Programmers Who Sometimes Make Mistakes

As you may well be aware, I am an excellent programmer. What you may not be aware of is that I SOMETIMES make mistakes. When one of these most uncommon events occur, I’ll often find myself ‘Undoing’ many steps to see what I had changed and what a particular piece of code looked like before I completely broke it. This opens you to the threat of a major UNDO-WTF; losing your work because you didn’t save and you hit “y” instead of Ctrl + Y (“z” instead of Cmd + shift + z on OSX).

Then we wrote Track Changes…

[Track changes](http://komodoide.com/blog/komodo-9-track-changes-no-more-undue-sorrows/) is a perfect feature for quickly reverting the changes that you’ve made during your current editing session. It will first use your files dirty state (changes that have not been saved) on your computer. If the file is under a code control tool like Git, it will use the last commit as it’s reference for what changes you’ve made.

This feature works with either the file on disk or your source code control tool to show you what’s been changed since your last save or your last commit, respectively.

These changes are indicated in the margin to the left of your code. It will show that you’ve added, removed, or changed a line. By clicking on these indicators you can then see what the change was, sharing it on [Kopy.io](http://kopy.io/) or revert the change.

[Komodo’s track changes](http://docs.komodoide.com/Manual/editor#editing_track-changes) is an innovative tool, built with our users’ speed and concentration in mind.