Received: by 10.66.78.40 with SMTP id y8mr9187905paw.9.1352815521170;
        Tue, 13 Nov 2012 06:05:21 -0800 (PST)
MIME-Version: 1.0
Path: 6ni79135pbd.1!nntp.google.com!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Patrick P Murphy <pmur...@nrao.edu>
Newsgroups: gnu.emacs.vm.info
Subject: Re: [VM] vm-mark-folder-modified-p
Date: Tue, 13 Nov 2012 09:04:42 -0500
Lines: 27
Message-ID: <mailman.12894.1352815520.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>
	<20640.50578.765000.491928@gargle.gargle.HOWL>
NNTP-Posting-Host: lists.gnu.org
X-Trace: usenet.stanford.edu 1352815520 20821 208.118.235.17 (13 Nov 2012 14:05:20 GMT)
X-Complaints-To: action@cs.stanford.edu
To: viewmail-i...@nongnu.org
Envelope-to: viewmail-i...@nongnu.org
X-NRAO-Sekrit: 3C273
X-Mailer: VM 8.2.0b under 23.3.1 (x86_64-pc-linux-gnu)
X-MailScanner-Information: Please contact postmas...@cv.nrao.edu for more
	information
X-MailScanner: Found to be clean
X-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-100.23,
	required 5, autolearn=disabled, RP_MATCHES_RCVD -0.23,
	USER_IN_WHITELIST -100.00)
X-MailScanner-From: pmur...@nrao.edu
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 192.33.115.2
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>

On Mon, 12 Nov 2012 09:46:58 +0000, 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 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.

Would a warning (inside vm-toggle-read-only) to the user be prudent
under this situation?  Something along the lines of "WARNING: you have
unsaved changes; marking this folder read-only may lose them" or similar
would certainly be enough to remind me that I'm, well, doing something
stupid :-)

Just a thought.

 - Pat

-- 
 Patrick P. Murphy, Ph.D.   Webmaster (East), Computing Security Manager
 http://www.nrao.edu/~pmurphy/          http://chien-noir.com/maze.shtml