From: Chong Yidong <cyd@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Jonathan Kamens <jik@kamens.us>, 11490@debbugs.gnu.org
Subject: bug#11490: vc-next-action overwrites changes in non-checked-out RCS file
Date: Fri, 04 Jan 2013 10:57:19 +0800 [thread overview]
Message-ID: <87txqxr6y8.fsf@gnu.org> (raw)
In-Reply-To: <xzsjesyiil.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 21 May 2012 23:57:54 -0400")
>> I'm obviously not in any position of authority here, but as for my
>> personal opinion, I would have no objection whatsoever to making
>> vc-mistrust-permissions default to true for safety's sake.
>
> Me neither. It seems like the default should be the safest mode of
> operation.
>
> However, Emacs 22.3 does not have this issuse; 23.1 onwards does.
> Something was lost with the removal of vc-next-action-on-file,
> and now vc-buffer-sync does not get called.
Can someone summarize again a *correct* recipe to see the bug? What
with the wrong initial bug report, and the imprecise follow-up, I can't
figure out where the problem lies. If I do
mkdir foo
cd foo
mkdir RCS
echo initial > file
ci -u -t-foo file
[Edit file in root]
emacs-24.0.96 -Q file
C-x v v
Then I get a prompt saying
File has unlocked changes. Claim lock retaining changes? (yes or no)
If I type yes, the changes are still there. What's the problem?
next prev parent reply other threads:[~2013-01-04 2:57 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
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 [this message]
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=87txqxr6y8.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=11490@debbugs.gnu.org \
--cc=jik@kamens.us \
--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 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).