Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
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)
Path: s9ni6964pbb.0!nntp.google.com!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Uday Reddy <usr.vm.ro...@gmail.com>
Newsgroups: gnu.emacs.vm.info
Subject: Re: [VM] vm-mark-folder-modified-p
Date: Mon, 12 Nov 2012 09:46:58 +0000
Lines: 35
Message-ID: <mailman.12785.1352713635.855.viewmail-info@nongnu.org>
References: <slrnk9uuu6.os6.jcb@coffee.inf.ed.ac.uk>
	<20640.45777.562000.496204@gargle.gargle.HOWL>
	<20640.49764.418168.592698@coffee.inf.ed.ac.uk>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
X-Trace: usenet.stanford.edu 1352713635 15746 208.118.235.17 (12 Nov 2012 09:47:15 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: viewmail-i...@nongnu.org
To: Julian Bradfield <jcb...@jcbradfield.org>
Envelope-to: viewmail-i...@nongnu.org
In-Reply-To: <20640.49764.418168.592698@coffee.inf.ed.ac.uk>
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
X-Received-From: 147.188.128.150
X-BeenThere: viewmail-i...@nongnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: General discussion of VM mail reader <viewmail-info.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/viewmail-info>,
	<mailto:viewmail-info-requ...@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/viewmail-info>
List-Post: <mailto:viewmail-i...@nongnu.org>
List-Help: <mailto:viewmail-info-requ...@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/viewmail-info>,
	<mailto:viewmail-info-requ...@nongnu.org?subject=subscribe>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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
> read-only.
> Perhaps there should be a variable: vm-read-only-includes-metadata or
> something!

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?

Cheers,
Uday