odd status caching behaviour with xls files
Bug #692829 reported by
yukihane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
Environment: Windows Standalone v2.2.1-3
1. Open committed Excel (not .xlsx but .xls) file.
2. Close this file without saving.
3. Run "bzr status". << No modified files exist.
This operation displays expected status, but following operation makes a file modfied.
1. Open committed Excel file.
2. Run "bzr status". << modified
3. Close this file without saving.
4. Run "bzr status". << keep modified!
tags: | added: dirstate win32 |
Changed in bzr: | |
importance: | Undecided → Low |
status: | Incomplete → Confirmed |
summary: |
- Once binary files modified, status-undo does not work. + odd status caching behaviour with xls files |
tags: | added: check-for-breezy |
To post a comment you must log in.
I guess that Excel is actually doing some auto-save type operation even if you don't explicitly save. Can you please make a copy of the file while excel is open, and again after you close it, and see if there are any binary differences between them.