From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: VC, read-only buffers for writable files
Date: Thu, 24 Oct 2002 12:54:17 -0400
Sender: emacs-devel-admin@gnu.org
Message-ID: <E184lFR-0005dn-00@fencepost.gnu.org>
References: <200210221331.g9MDV3n21931@rum.cs.yale.edu>  <E184FgT-0007id-00@fencepost.gnu.org> <200210230739.g9N7dex06199@rum.cs.yale.edu>
Reply-To: rms@gnu.org
NNTP-Posting-Host: main.gmane.org
X-Trace: main.gmane.org 1035478603 4141 80.91.224.249 (24 Oct 2002 16:56:43 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Thu, 24 Oct 2002 16:56:43 +0000 (UTC)
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org,
	spiegel@gnu.org
Return-path: <emacs-devel-admin@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 184lHl-00014X-00
	for <emacs-devel@main.gmane.org>; Thu, 24 Oct 2002 18:56:41 +0200
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian))
	id 184lK1-0001gt-00
	for <emacs-devel@quimby.gnus.org>; Thu, 24 Oct 2002 18:59:02 +0200
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 184lGN-0005oX-00; Thu, 24 Oct 2002 12:55:15 -0400
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 184lFU-0004ZE-00
	for emacs-devel@gnu.org; Thu, 24 Oct 2002 12:54:20 -0400
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 184lFS-0004YE-00
	for emacs-devel@gnu.org; Thu, 24 Oct 2002 12:54:20 -0400
Original-Received: from fencepost.gnu.org ([199.232.76.164])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 184lFR-0004XP-00
	for emacs-devel@gnu.org; Thu, 24 Oct 2002 12:54:17 -0400
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.10)
	id 184lFR-0005dn-00; Thu, 24 Oct 2002 12:54:17 -0400
Original-To: monnier+gnu/emacs@rum.cs.yale.edu
In-reply-to: <200210230739.g9N7dex06199@rum.cs.yale.edu>
	(monnier+gnu/emacs@rum.cs.yale.edu)
Errors-To: emacs-devel-admin@gnu.org
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Post: <mailto:emacs-devel@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
List-Id: Emacs development discussions. <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel/>
Xref: main.gmane.org gmane.emacs.devel:8739
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8739

    Sorry that should have been `buffer'.

    >     better that way for the user.  More specifically, it makes it read-only
    >     if the file seems to be locked by another user.
    > 
    > Under RCS, the file is read-only whenever the file is not locked by you.
    > I think that is the right way to handle it.

I also meant `buffer'.

    If the file is indeed read-only, then everything works as expected,
    but the VC code also tries to make the buffer read-only when the file
    is locked by someone else and yet is writable.

I think that is correct--and useful.  If VC is mistaken, you can use
C-x C-q to make the buffer writable.