unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Jonathan Kamens <jik@kamens.us>
Cc: 11490@debbugs.gnu.org
Subject: bug#11490: vc-next-action overwrites changes in non-checked-out RCS file
Date: Wed, 16 May 2012 16:12:40 -0400	[thread overview]
Message-ID: <iwobpnx4uf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4FB40003.3050502@kamens.us> (Jonathan Kamens's message of "Wed,  16 May 2012 15:29:07 -0400")

Jonathan Kamens wrote:

> GNU Emacs 24.0.95.1 (x86_64-redhat-linux-gnu, GTK+ Version 2.24.10) of
> 2012-04-06 on x86-13.phx2.fedoraproject.org
>
> Make an RCS file writable with chmod +w without locking it.
>
> Make changes to the file.
>
> Type C-x v v.
>
> The file will be locked and checked out and your changes will be
> overwritten.

I cannot reproduce this. I did:


mkdir foo
cd foo
mkdir RCS
echo initial > file
ci -u -t-foo file
chmod +w file
emacs-24.0.96 -Q file
add some text to file
C-x v v

A log buffer appears. I enter some text and press C-c C-c.
I am told the buffer is modified and prompted to save it. I do so.

At this point, RCS returns an error:

  RCS/file,v  <--  file
  ci: RCS/file,v: no lock set by gmorris for revision 1.1

The contents of the file on disk and in the Emacs buffer are unchanged
(ie, the added text is still present).


This was with RCS 5.7. I never normally use RCS, maybe I am missing
something.

Do you have a recipe starting from emacs -Q that shows the problem?





  reply	other threads:[~2012-05-16 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 19:29 bug#11490: vc-next-action overwrites changes in non-checked-out RCS file Jonathan Kamens
2012-05-16 20:12 ` Glenn Morris [this message]
2012-05-17  1:17   ` Jonathan Kamens
2012-05-18  0:45     ` Glenn Morris
2012-05-18 14:38       ` Jonathan Kamens
2012-05-22  3:57         ` Glenn Morris
2013-01-04  2:57           ` Chong Yidong
2013-01-04  3:11             ` Glenn Morris
2013-01-04  3:17               ` Jonathan Kamens
2013-01-04  3:21                 ` Glenn Morris
2013-01-04  3:33                   ` Jonathan Kamens
2013-01-05  9:35                     ` Chong Yidong

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=iwobpnx4uf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=11490@debbugs.gnu.org \
    --cc=jik@kamens.us \
    /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).