From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.devel Subject: VC, read-only buffers for writable files Date: Tue, 22 Oct 2002 09:31:03 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <200210221331.g9MDV3n21931@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035293530 4307 80.91.224.249 (22 Oct 2002 13:32:10 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 22 Oct 2002 13:32:10 +0000 (UTC) Cc: spiegel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 183z8i-000179-00 for ; Tue, 22 Oct 2002 15:32:08 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 183z9w-0000vq-00 for ; Tue, 22 Oct 2002 15:33:24 +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 183z8u-000077-00; Tue, 22 Oct 2002 09:32:20 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 183z7m-0006kU-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 09:31:10 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 183z7j-0006k3-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 09:31:09 -0400 Original-Received: from rum.cs.yale.edu ([128.36.229.169]) by monty-python.gnu.org with esmtp (Exim 4.10) id 183z7g-0006j6-00; Tue, 22 Oct 2002 09:31:04 -0400 Original-Received: (from monnier@localhost) by rum.cs.yale.edu (8.11.6/8.11.6) id g9MDV3n21931; Tue, 22 Oct 2002 09:31:03 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 Original-To: emacs-devel@gnu.org Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:8647 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8647 It had been decided to postpone the decision to post-21.1, so I think it's time to make a decision now. Currently VC sometimes makes a file read-only because it thinks it's better that way for the user. More specifically, it makes it read-only if the file seems to be locked by another user. This can cause problems when VC gets the lock's ownership wrong or when people are purposefully setting up access rights such that anybody who's part of a particular group should be able to edit the checked-out file. It might be able to help the user avert a mistake in a few cases, but that's only if the file's permissions are setup incorrectly. If the file's permissions are not setup properly, then the user will probably encounter many other risks anyway so what should happen in this case is that the permissions should be fixed. But Emacs has no way to tell whether the discrepency is because the user has set things up in a slightly non-standard way, or whether it's because Emacs is confused, or whether it's indeed because the file should be read-only. This special behavior used to apply to SCCS, RCS and CVS under Emacs-20 and was silently changed in Emacs-21 to only apply to RCS and SCCS (it was changed as a side effect of another change). Nobody complained about this change and I think we should go further and remove this hack altogether so it doesn't aply to RCS and SCCS either. Stefan