Loading Profile...
Unsaved edits warning when there are none
When I save a document in my text editor that is open (via the Versions SVN client app) but unchanged in Changes, I get the "There are also unsaved edits in Changes" warning even though there are no such unsaved edits.
I would really like Changes to silently reload the document from disk in these cases.
I would really like Changes to silently reload the document from disk in these cases.
I’m unchanged
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Just to be clear, the workflow is:
1. Diff the document in Changes, via Versions
2. Edit that document independently of either Changes or Versions
3. Activate Changes (via Versions again or just by switching to it?)
4. Get unsaved edits warning in Changes?
Is that correct?
Thanks,
Fraser -
Inappropriate?Yes, that's exactly my workflow.
Regarding 3.), I just switch back to Changes directly via Cmd-Tab.
BTW I also tried it in isolation in Changes directly, no Versions app involved, and the same thing happens:
1.) echo foo > test1.txt
2.) echo bar > test2.txt
3.) chdiff test{1,2}.txt
4.) (Changes activates. Do not change anything and switch back to Terminal)
5.) echo baz > test2.txt
Now switch back to Changes. The warning appears even though nothing was changed in Changes in step 4. It also appears if you just use the touch command in step 5.
It also happens when using the New Session menu command instead of the chdiff command.
When I'm preparing a commit, I use Changes to go through all the changes to clean up some of them that are just artifacts of the editing process, for example random whitespace changes, TODO markers etc. That means a lot of back and forth between Changes and Xcode. Every time I fix something in Xcode and then return to Changes, I have to click the Revert button. -
Inappropriate?This problem is really starting to get in my way and my guess is that the fix wouldn't be too hard to implement. Were you able to verify it and is there a timeline for a minor update?
I apologize for being pushy but this one *is* annoying.
EMPLOYEE
