From: Jonathan Kamens <jik@kamens.us>
To: Glenn Morris <rgm@gnu.org>
Cc: 11490@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#11490: vc-next-action overwrites changes in non-checked-out RCS file
Date: Thu, 03 Jan 2013 22:17:42 -0500 [thread overview]
Message-ID: <50E649D6.4090808@kamens.us> (raw)
In-Reply-To: <ui7gnttzg4.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
On 01/03/2013 10:11 PM, Glenn Morris wrote:
> Chong Yidong wrote:
>
>> Can someone summarize again a *correct* recipe to see the bug?
> mkdir foo
> cd foo
> mkdir RCS
> echo initial > file
> ci -u -t-foo file
> emacs-24.2 -Q file
>
> M-x toggle-read-only
>
> Enter some text in the buffer, eg now it looks like:
>
> -----
> initial
> foobar
> -----
>
> Press C-x v v, and "foobar" is deleted with no prompting and no way to
> get it back.
>
> I changed vc-mistrust-permissions to t for 24.3 because of this.
> But now that I check, it doesn't seem to help...
The problem described above may indeed be a problem, but it's not the
problem I reported.
The problem I reported is:
mkdir foo
cd foo
mkdir RCS
echo initial > file
ci -u -t-foo file
chmod +w file
echo second >> file
chmod -w file
emacs -Q file
C-x v v - the changes are overwritten without prompting
I think the step missing from Chong Yidong's recipe was making sure the
file is read-only before trying to edit it in emacs.
If vc-mistrust-permissions is true by default then this issue doesn't occur.
jik
[-- Attachment #2: Type: text/html, Size: 1618 bytes --]
next prev parent reply other threads:[~2013-01-04 3: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
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 [this message]
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=50E649D6.4090808@kamens.us \
--to=jik@kamens.us \
--cc=11490@debbugs.gnu.org \
--cc=cyd@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 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).