all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jonathan Kamens <jik@kamens.us>
To: Glenn Morris <rgm@gnu.org>
Cc: 11490@debbugs.gnu.org
Subject: bug#11490: vc-next-action overwrites changes in non-checked-out RCS file
Date: Wed, 16 May 2012 21:17:34 -0400	[thread overview]
Message-ID: <4FB451AE.60508@kamens.us> (raw)
In-Reply-To: <iwobpnx4uf.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

Try it without making the file writable.

This happens, e.g., if a file is edited as root by a user using vim, 
which doesn't care whether it's writable or not, since it's root doing 
the editing, and then by a user using Emacs, which /does/ care because 
it detects VC and thus makes the file read-only in Emacs. The user's 
first impulse will be to type C-x v v, which will overwrite the previous 
editor's changes.

The problem goes away when vc-mistrust-permissions is set to true.

I would argue that C-x v v should always check the status of a file with 
vc-mistrust-permissions set to true (or the logical equivalent) before 
overwriting its contents and potentially losing data.

   jik


[-- Attachment #2: Type: text/html, Size: 975 bytes --]

  reply	other threads:[~2012-05-17  1:17 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
2012-05-17  1:17   ` Jonathan Kamens [this message]
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

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

  git send-email \
    --in-reply-to=4FB451AE.60508@kamens.us \
    --to=jik@kamens.us \
    --cc=11490@debbugs.gnu.org \
    --cc=rgm@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 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.