unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org, spiegel@gnu.org
Subject: Re: VC, read-only buffers for writable files
Date: Thu, 24 Oct 2002 13:03:36 -0400	[thread overview]
Message-ID: <200210241703.g9OH3bA15321@rum.cs.yale.edu> (raw)
In-Reply-To: E184lFR-0005dn-00@fencepost.gnu.org

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

Problem is: it happens very rarely since RCS normally makes sure the file
is not writable by anybody but the true user.  And when it happens it's too
often because VC is confused about the identity of the owner of the lock.
Every few months a user complains about this behavior in VC and it's
difficult to fix.


	Stefan

      reply	other threads:[~2002-10-24 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 13:31 VC, read-only buffers for writable files Stefan Monnier
2002-10-22 14:35 ` Andre Spiegel
2002-10-22 14:49   ` Stefan Monnier
2002-10-23  7:12 ` Richard Stallman
2002-10-23  7:39   ` Stefan Monnier
2002-10-24 16:54     ` Richard Stallman
2002-10-24 17:03       ` Stefan Monnier [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=200210241703.g9OH3bA15321@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=spiegel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).