GNU bug report logs - #3916
23.1.50; vc with rcs prompt for commit when it shouldn't.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 3916 in the body.
You can then email your comments to 3916 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.1.50; vc with rcs prompt for commit when it shouldn't. 
Date: Fri, 24 Jul 2009 09:42:15 +0200

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Hi,
here a little recipe of what i think is wrong:

1) find-file ==> my_file

2) C-x v i ==> register my_file under rcs

3) C-x v v ==> co my_file
   ==>No files remain to be committed

4) C-x v v ==> co again, ok my_file is no more read only and ready to
   edit.

5) make some changes to my_file (these changes are not finished i don't
   want to commit them).

6) For some reason, save buffer and kill buffer.

7) find-file ==> my_file:
   - The file is locked again (read-only) ==> why? (was not doing that
   before until file was commited or reverted)

8) Try to co the file:
   C-x v v ==> The commit buffer pop out and ask me to commit ==> Why?
   I don't want to commit these unfinished changes to my_file.

9) i must kill the commit buffer and toggle-read-only the file to be
   able to edit it.
   Even if i run the shell command co -l -q -f my_file (that add write
   permission on file) vc turn file read-only.

Note:This happen even with emacs -Q

WDYT



   

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/share/emacs/23.1.50/etc/DEBUG for instructions.


In GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.16.1)
 of 2009-07-12 on tux
Windowing system distributor `The X.Org Foundation', version 11.0.10503000
configured using `configure  '--prefix=/usr' '--build=i686-pc-linux-gnu' '--host=i686-pc-linux-gnu' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--program-suffix=-emacs-23' '--infodir=/usr/share/info/emacs-23' '--with-sound' '--with-x' '--without-toolkit-scroll-bars' '--with-gif' '--with-jpeg' '--with-png' '--with-rsvg' '--with-tiff' '--with-xpm' '--with-xft' '--without-libotf' '--without-m17n-flt' '--with-x-toolkit=gtk' '--without-hesiod' '--without-kerberos' '--without-kerberos5' '--with-gpm' '--with-dbus' 'build_alias=i686-pc-linux-gnu' 'host_alias=i686-pc-linux-gnu' 'CFLAGS=-march=i686 -pipe -O2' 'LDFLAGS=-Wl,-O1''

Important settings:
  value of $LC_ALL: fr_FR.UTF-8
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: fr_FR.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Python

Minor modes in effect:
  icomplete-mode: t
  icicle-mode: t
  delete-selection-mode: t
  minibuffer-depth-indicate-mode: t
  auto-image-file-mode: t
  partial-completion-mode: t
  show-paren-mode: t
  display-battery-mode: t
  display-time-mode: t
  diff-auto-refine-mode: t
  shell-dirtrack-mode: t
  recentf-mode: t
  savehist-mode: t
  desktop-save-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
e t <up> <left> <left> <left> <left> <left> <left> 
<left> <left> <left> <left> <left> <left> <left> <left> 
q f <right> <right> <right> <right> <right> <right> 
<right> <right> <right> <right> <right> <right> <right> 
<right> <return> <up> <left> <left> <left> <left> <left> 
<left> <left> <left> <left> <left> <left> <left> <left> 
<left> <left> <left> SPC - <right> SPC - <right> <right> 
<right> <right> <right> <right> <right> <right> <right> 
<right> <right> <right> <right> <right> <right> <return> 
<S-up> g <S-down> <up> <left> <left> <left> <left> 
<left> <left> <left> <left> <left> <left> <left> <left> 
<left> <left> <left> <left> <left> <left> <left> <left> 
<backspace> u <return> <S-up> g <S-down> a l i a s 
SPC r c s - c o <return> <up> SPC c o SPC - l SPC - 
q SPC - f SPC \ $ 1 <return> r c s - c o SPC p i l 
_ <tab> <return> <S-up> <return> C-x v v C-x v v C-x 
k <return> g <return> C-x k <return> <S-down> <up> 
<return> <S-up> g <return> C-x C-& M-x v c - t o g 
<tab> <return> r r r <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> M-> 
M-x b u f f e r - t o g <tab> <tab> <backspace> <backspace> 
<backspace> r e <tab> <tab> C-g M-x t o g l e <backspace> 
<backspace> <tab> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <return> <down> <down> <down> <down> 
<down> <down> <down> <down> <down> <down> <down> <down> 
<down> <down> <down> <down> <up> <up> <up> C-x k <return> 
q <return> C-x v v M-x r e p o <tab> <down> <retur
n>

Recent messages:
Buffer is read-only: #<buffer pil_viewer.py> [3 times]
Mark set
Computing completion candidates... [5 times]
File is under version-control; use C-x v v to check in/out
No prefix completions
icicle-abort-recursive-edit: No recursive edit is in progress
Local value of py-indent-offset set to 4
Using the CPython shell
No files remain to be committed
Computing completion candidates...

-- 
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France

Message #10 received at 3916-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
Cc: 3916-done <at> debbugs.gnu.org
Subject: Re: bug#3916: 23.1.50; vc with rcs prompt for commit when it shouldn't.
Date: Fri, 24 Jul 2009 07:01:57 -0700 (PDT)

Thierry Volpiatto <thierry.volpiatto <at> gmail.com> writes:

  > Please write in English if possible, because the Emacs maintainers
  > usually do not have translators to read other languages for them.
  > 
  > Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.
  > 
  > Please describe exactly what actions triggered the bug
  > and the precise symptoms of the bug:
  > 
  > Hi,
  > here a little recipe of what i think is wrong:
  > 
  > 1) find-file ==> my_file
  > 
  > 2) C-x v i ==> register my_file under rcs
  > 
  > 3) C-x v v ==> co my_file
  >    ==>No files remain to be committed
  > 
  > 4) C-x v v ==> co again, ok my_file is no more read only and ready to
  >    edit.
  > 
  > 5) make some changes to my_file (these changes are not finished i don't
  >    want to commit them).
  > 
  > 6) For some reason, save buffer and kill buffer.
  > 
  > 7) find-file ==> my_file:
  >    - The file is locked again (read-only) ==> why? (was not doing that
  >    before until file was commited or reverted)
  > 
  > 8) Try to co the file:
  >    C-x v v ==> The commit buffer pop out and ask me to commit ==> Why?
  >    I don't want to commit these unfinished changes to my_file.
  > 
  > 9) i must kill the commit buffer and toggle-read-only the file to be
  >    able to edit it.
  >    Even if i run the shell command co -l -q -f my_file (that add write
  >    permission on file) vc turn file read-only.
  > 
  > Note:This happen even with emacs -Q
  > 
  > WDYT
  > 
  > 
  > 
  >    
  > 
  > If Emacs crashed, and you have the Emacs process in the gdb debugger,
  > please include the output from the following gdb commands:
  >     `bt full' and `xbacktrace'.
  > If you would like to further debug the crash, please read the file
  > /usr/share/emacs/23.1.50/etc/DEBUG for instructions.
  > 
  > 
  > In GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.16.1)
  >  of 2009-07-12 on tux
 ^^^^^^^^^^^^^^^^^^^^^^^^
Your source is too old, this was a temporary bug is already fixed.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.