unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Andre Spiegel <spiegel@gnu.org>, emacs-devel@gnu.org
Subject: Re: Disabling VC:  Documentation seems inadequate.
Date: 04 Dec 2003 11:00:22 -0500	[thread overview]
Message-ID: <jwvad68h8za.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <Pine.LNX.3.96.1031204083213.226B-100000@acm.acm>

> I mentioned this in summer of 2002, and you took on the task of polling
> users on the issue of what C-x C-q should do (thanks!).  It turned out
> that my feeling wasn't that widespread - it was my problem.  So, of
> course, I bound C-x C-q to `toggle-read-only' in my own .emacs.

Your recollection is incorrect: In Emacs-CVS C-x C-q is now bound to
toggle-read-only.

> (i) Sometimes my files (checked out from SourceForge under CVS control),
> get loaded into RO buffers, despite the files being writeable.  I haven't
> investigated why;
> (ii) Sometimes Emacs has signalled an error on C-x C-s.  This occurred on
> Emacs 21.1, but seems to have been fixed for 21.3.  It happened after I'd
> edited a buffer, then renamed the file to a "backup" name (e.g. mv
> cc-awk.el cc-awk.191103.el) before doing C-x C-s; (I used mv rather than
> cp so as to preserve the file's timestamp).

> Now this is all probably "pilot error", but it's hassle which appears not
> to bring me any benefit.

If it's related to VC and you were not using VC, then it's definitely not
a pilot error but a bug in VC (or maybe a feature, but in that case maybe
we should reconsider its classification).
So please report those problems so we can fix them.


        Stefan

  reply	other threads:[~2003-12-04 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 20:45 Disabling VC: Documentation seems inadequate Alan Mackenzie
2003-12-03 20:59 ` Stefan Monnier
2003-12-03 21:02 ` Andre Spiegel
2003-12-04 12:46   ` Alan Mackenzie
2003-12-04 16:00     ` Stefan Monnier [this message]
2003-12-05 17:07     ` Andre Spiegel

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=jwvad68h8za.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    --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).