VM

vm-quit-no-change leaves behind an auto-save file

Bug #502683 reported by Uday Reddy
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
Low
Uday Reddy

Bug Description

The command vm-quit-no-change (normally bound to 'x') is leaving behind an auto-save file. I would expect that one would normally use this command if one wants to lose the changes made to a folder. So, having a copy of these changes on the disk is probably of no point.

So, I am considering changing the vm-quit-no-change command to destroy the auto-save file. I will also add a variable vm-preserve-auto-save-on-exit to allow the old behaviour for people that want it.

Related branches

lp:vm
Revision history for this message
Uday Reddy (reddyuday) wrote :

This could be a bug in Emacs. delete-auto-save-file-if-necessary is not doing its job. The C function recent-auto-save-p is returning nil. However, the C function kill-buffer gets rid of the auto-save file any way. Strange!

Changed in vm:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Uday Reddy (reddyuday)
Revision history for this message
Uday Reddy (reddyuday) wrote :

Sidestepped the Emacs madness by doing our own deletion after confirmation from the user.

Changed in vm:
status: Confirmed → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.