On Mon, 12 Nov 2012 09:46:58 +, Uday Reddy usr.vm.ro...@gmail.com said:
I have now modified `vm-quit' in the trunk to silently discard any
changes to the folder (meta-data) if the folder is read-only.
There are a couple of things about this that worry me.
1. If you do
Uday Reddy usr.vm.ro...@gmail.com wrote:
Rethinking this issue, I think there has been a general misunderstanding of
what it means for a folder to be visited read-only. As the doc string of
`vm-visit-folder' says, visiting a folder read-only just means that no
attribute changes, messages
On 2012-11-12, Uday Reddy usr.vm.ro...@gmail.com wrote:
I have now modified `vm-quit' in the trunk to silently discard any changes
to the folder (meta-data) if the folder is read-only.
There are a couple of things about this that worry me.
1. If you do vm-toggle-read-only for some reason or
Julian Bradfield writes:
Returning to the problem noted a while ago of VM marking a read-only
folder modified when it upgrades attribute data:
Is there *any* case in which vm-mark-folder-modified-p should work on
a read-only folder?
Good thinking, Julian. This should be a good place to
