GNU bug report logs -
#9781
read-only prompt in vc-next-action
Previous Next
Reported by: Jan Djärv <jan.h.d <at> swipnet.se>
Date: Tue, 18 Oct 2011 06:39:02 UTC
Severity: minor
Found in version 24.0.90
Fixed in version 24.3
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #14 received at 9781 <at> debbugs.gnu.org (full text, mbox):
Jan Djärv wrote:
> In a bzr repository, do
> % bzr rm some-file
>
> and modify some other file.
>
> Then in Emacs, do vc-dir on the directory where the file was.
> Mark the file that is listed as removed. Also mark the edited file.
> Press v.
>
> Expected result: I can type in a log message and commit.
> Real result: A prompt in the minibuffer appears:
> some-file is edited but read-only; make it writable and continue? (y/n)
Fixed. Now you will be able to commit (and then get bug#3214).
Actually the problem only happens with removed directories (because
file-writable-p also returns non-nil if a file can be created).
Recipe:
mkdir /tmp/foo
cd /tmp/foo
bzr init
mkdir subdir
touch file subdir/subfile
bzr add
bzr commit -m "c1"
bzr remove subdir
echo 1 >> file
emacs -Q
M-x vc-dir RET
M
v
> Also, the choices in the question should be three:
>
> 1 Make writable and continue.
> 2 Don't make writable and continue
> 3 Abort
Isn't ctrl-g good enough for aborting, rather than introducing a 3-state
question?
This bug report was last modified 12 years and 241 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.