vm-delete-postponed-message is too heavy handed
Bug #1459490 reported by
Mark Diekhans
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VM |
Fix Committed
|
High
|
Uday Reddy |
Bug Description
I have recently lost copys messages being composed in steps using vm-pine . I believe this is caused by somethingcausing vm-delete-
vm-delete-
This seems very heavy handed to purge all deleted message and then save the folder. It seems far better behavior
to just mark the message as deleted.
Happy to submit a patch, however I would like to understand the motivation of expunging. I would just like to drop these two lines, or at very least, the expunge
Changed in vm: | |
assignee: | nobody → Uday Reddy (reddyuday) |
milestone: | none → 8.2.0b1 |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: add-ons |
tags: | added: 8.0 |
Changed in vm: | |
milestone: | 8.3.1a → 8.2.1a |
Changed in vm: | |
milestone: | 8.2.1a → 8.2.90a |
To post a comment you must log in.
this seems to be related to this comment, however it's not clear why this is true:
;; If you have postponed messages you will be asked if you want to continue folder'
;; composing them, if you say "yes" you will visit the `vm-postponed-
;; and you can select the message you would like to continue and press "m"
;; again! However be aware this works currently only if you expunge all
;; messages marked for deletion and save the postponed folder.