Suggestion: Make 'remove' in treewidget work like 'delete' in bzr-explorer Status pane
Bug #779675 reported by
Martitza
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar Explorer |
Confirmed
|
Medium
|
Unassigned | ||
| QBzr |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
The behavior of the pop-up context-menu option 'remove' in the qbzr treewidget as integrated with bzr-explorer as the WorkingTree pane seems to clash with the behavior of the 'delete' action in the bzr-explorer Status pane.
Whereas the Status pan 'delete' action actually moves an object to the trash, the WorkingTree 'remove' action simply renames the object (e.g. myfile.c => myfile.c.~1~) so taht it is ignored by bzr-explorer but still exists on disk.
I'm not sure which behavior is preferable, but Ithink they should be consistent with each other.
| affects: | qbzr → bzr-explorer |
| affects: | bzr-explorer → qbzr |
| Changed in qbzr: | |
| status: | New → Confirmed |
| Changed in bzr-explorer: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in qbzr: | |
| importance: | Undecided → Medium |
To post a comment you must log in.
