Message from discussion vm-mark-folder-modified-p
Received: by 10.66.86.98 with SMTP id o2mr7016509paz.29.1352713635867;
Mon, 12 Nov 2012 01:47:15 -0800 (PST)
From: Uday Reddy <usr.vm.ro...@gmail.com>
Subject: Re: [VM] vm-mark-folder-modified-p
Date: Mon, 12 Nov 2012 09:46:58 +0000
X-Trace: usenet.stanford.edu 1352713635 15746 184.108.40.206 (12 Nov 2012 09:47:15 GMT)
To: Julian Bradfield <jcb...@jcbradfield.org>
X-Mailer: VM 8.2.0b under 24.2.1 (i386-mingw-nt5.1.2600)
X-detected-operating-system: by eggs.gnu.org: Solaris 10
List-Id: General discussion of VM mail reader <viewmail-info.nongnu.org>
Content-Type: text/plain; charset=us-ascii
Julian Bradfield writes:
> I see the point: from vm's point of view, it may treat the data as
> read-only, but change the meta-data, just as visiting a file read-only
> may update its last access time.
> However, I would expect most people to associate vm visiting a folder
> read-only with emacs visiting a file read-only with opening a file
> Perhaps there should be a variable: vm-read-only-includes-metadata or
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 other, you might put the
folder in read-only mode. If you forget that you have done so and quit the
folder, the changes that were made before putting it in read-only mode would
be lost. So, vm-toggle-read-only has now become a mildly unsafe operation.
2. I think I have seen `vm-save-message' write the message to a visited
folder inside VM instead of the folder on disk. (I think I have enjoyed
this 'feature' on occasion when I was on a slow network.) I don't know what
happens if that folder has been visited read-only. Can somebody please
check this situation?