From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Alan Mackenzie <none@example.invalid>
Newsgroups: gmane.emacs.bugs
Subject: How am I supposed to make a buffer read-only?
Date: Sat, 1 Jun 2002 14:50:13 +0000
Organization: muc.de e.V. -- private internet access
Sender: bug-gnu-emacs-admin@gnu.org
Message-ID: <5vmada.u5.ln@acm.acm>
NNTP-Posting-Host: localhost.gmane.org
X-Trace: main.gmane.org 1022944892 19187 127.0.0.1 (1 Jun 2002 15:21:32 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sat, 1 Jun 2002 15:21:32 +0000 (UTC)
Return-path: <bug-gnu-emacs-admin@gnu.org>
Original-Received: from hermes.netfonds.no ([80.91.224.195])
	by main.gmane.org with esmtp (Exim 3.33 #1 (Debian))
	id 17EAh9-0004zM-00
	for <gnu-bug-gnu-emacs@gmane.org>; Sat, 01 Jun 2002 17:21:31 +0200
Original-Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164])
	by hermes.netfonds.no (8.12.1/8.12.1) with ESMTP id g51FL5uM000521
	for <gnu-bug-gnu-emacs@m.gmane.org>; Sat, 1 Jun 2002 17:21:05 +0200 (CEST)
Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
	by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian))
	id 17EAgh-0008L6-00; Sat, 01 Jun 2002 11:21:03 -0400
Original-Received: from marvin.muc.de ([193.149.48.2])
	by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian))
	id 17EAfp-0008Jg-00
	for <gnu-emacs-bug@prep.ai.mit.edu>; Sat, 01 Jun 2002 11:20:09 -0400
Original-Received: (qmail 72275 invoked by uid 8); 1 Jun 2002 15:19:13 -0000
Original-To: gnu-emacs-bug@prep.ai.mit.edu
Original-Path: not-for-mail
Original-Newsgroups: gnu.emacs.bug
Original-Lines: 35
Original-NNTP-Posting-Host: acm.muc.de
Original-X-Trace: marvin.muc.de 1022944753 72271 193.149.49.134 (1 Jun 2002 15:19:13 GMT)
Original-X-Complaints-To: news-admin@muc.de
Original-NNTP-Posting-Date: 1 Jun 2002 15:19:13 GMT
User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.0.35 (i686))
Errors-To: bug-gnu-emacs-admin@gnu.org
X-BeenThere: bug-gnu-emacs@gnu.org
X-Mailman-Version: 2.0.9
Precedence: bulk
List-Help: <mailto:bug-gnu-emacs-request@gnu.org?subject=help>
List-Post: <mailto:bug-gnu-emacs@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-request@gnu.org?subject=subscribe>
List-Id: Bug reports for GNU Emacs,
	the Swiss army knife of text editors <bug-gnu-emacs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-gnu-emacs>,
	<mailto:bug-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-gnu-emacs/>
Xref: main.gmane.org gmane.emacs.bugs:1738
X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:1738

Gnu Emacs 21.1

I just tried C-x C-q, and got the error message back: "/my/path/foo.el is
up-to-date" in the minibuffer.  [foo.el is a CVSed file.]

Bug:  The buffer remained writable.
[Possibly relevant:  the cvs server is at the other end of a modem
connection which wasn't up at the time, thankfully.]

A quick C-h k revealed that the normal, simple, sane, sensible binding
has been overridden by vc-toggle-read-only, a mis-named function if ever
there were one.  It seems to regard checking a file in as a perfectly
sensible "method" of making it's buffer read-only.  Ye Gods!

Is there really some semantic identity between changing the read-only
status of a buffer, and checking it's file about?  Damned if I can see
it.  Particularly when the version control system is CVS.  I thought it
was only commercial version control systems that were lazy/fascistic
enough to (ab)use files' read-only status to mark their check-outedness.

Checking a file in/out is one thing.  Changing the read-only status of a
buffer is something completely different.  Surely?  Somebody please tell
me I'm having a bad dream, and I'll wake up soon.

Do I really have to type M-x toggle-read-only for evermore, so as to
avoid the risk of accidentally checking a file in/out? 

Suggestion:  C-x C-q should be reserved for toggle-read-only, and
something else (C-x v v, presumably) for checking files in/out.

-- 
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").