NoChangesError is thrown for various bzr errors
Bug #717378 reported by
Cody A.W. Somerville
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zim |
Won't Fix
|
High
|
Unassigned |
Bug Description
When saving a new version and the notebook's bzr branch is binded and out of date with the master branch, NoChangesError is thrown. Zim only checks to see if the error code is 3 to determine if it should throw this error or not which is incorrect as 3 is used to indicate many different failures. The end result is that your changes don't get saved and Zim telling you incorrectly that there are no new changes to save.
Changed in zim: | |
status: | New → Confirmed |
importance: | Undecided → High |
To post a comment you must log in.
From duplicate: this also happens e.g. when "whoami" is not set etc.