Public bug reported:
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.
** Affects: vm
Importance: Low
Assignee: Uday Reddy (reddyuday)
Status: Confirmed
** Changed in: vm
Status: New => Confirmed
** Changed in: vm
Importance: Undecided => Low
** Changed in: vm
Assignee: (unassigned) => Uday Reddy (reddyuday)
--
vm-quit-no-change leaves behind an auto-save file
https://bugs.launchpad.net/bugs/502683
You received this bug notification because you are a member of VM
development team, which is the registrant for VM.
Status in VM (View Mail) for Emacs: Confirmed
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.
_______________________________________________
Mailing list: https://launchpad.net/~vm
Post to : [email protected]
Unsubscribe : https://launchpad.net/~vm
More help : https://help.launchpad.net/ListHelp
