all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <none@example.invalid>
Subject: How am I supposed to make a buffer read-only?
Date: Sat, 1 Jun 2002 14:50:13 +0000	[thread overview]
Message-ID: <5vmada.u5.ln@acm.acm> (raw)

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").

             reply	other threads:[~2002-06-01 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 14:50 Alan Mackenzie [this message]
2002-06-02  2:52 ` How am I supposed to make a buffer read-only? Richard Stallman
2002-06-02 13:26   ` Andre Spiegel
2002-06-03 11:42     ` Richard Stallman
2002-06-03 14:01     ` Francesco Potorti`

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5vmada.u5.ln@acm.acm \
    --to=none@example.invalid \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.