Kepler: unsaved changes management policy is not natural
SITUATION: a change is made in any editor
PROBLEM: closing any editor (even another than the one where the change happened) triggers a “There are unsaved changes, do you want to save them?” dialog
->This is really annoying and counter-intuitive because the closed editor has nothing to do with the change
(from redmine: issue id 1887, created on 2014-01-13, closed on 2014-07-07)