Re: PCL-CVS: `A' removes cvs-mode from buffer *cvs*

[Stefan Monnier]

> Now, for the first time, I saw it on GNU/Linux as well.

OK.  So at least we know it's not specific to Windows.

> | Wrote [...]/cvs-EMACS_22_BASE/emacs/lisp/ChangeLog
> | (No files need saving)
> | Running cvs update ...
> | add-change-log-entry-other-window: Buffer is read-only: #<buffer 
> *cvs*[emacs/lisp]<2>>
> | Saving file [...]/cvs-EMACS_22_BASE/emacs/lisp/ChangeLog...
> | Wrote [...]/cvs-EMACS_22_BASE/emacs/lisp/ChangeLog
> | error in process sentinel: cvs-sentinel: Symbol's value as variable is 
> void: cvs-cookies
> | error in process sentinel: Symbol's value as variable is void: cvs-cookies
> | Mark set [3 times]
> | insert-for-yank: Buffer is read-only: #<buffer *cvs*[emacs/lisp]<2>>
> | Mark set
> | insert-for-yank: Buffer is read-only: #<buffer *cvs*[emacs/lisp]<2>>
> | Mark set
> | insert-for-yank: Buffer is read-only: #<buffer *cvs*[emacs/lisp]<2>>
> | ((lambda nil (add-hook (quote change-major-mode-hook) (quote debug) nil t)) 
> (lambda nil (rename-buffer (generate-new-buffer-name ...)) (local-set-key 
> (kbd "RET") (lambda ... ... ...)) (local-set-key (kbd "~") (lambda ... ... 
> ...)) (local-set-key (kbd "*") (lambda nil ... ...))))

> The last one was after evaluating your suggestion (see below).  The
> other hooks are not relevant to the problem, because I don't use them
> on the Windows machine.

Could you tell me what you've done during the above time, in which order.
Ideally correlate the above messages with the actions you've taken?
It looks like you've first run cvs(-mode)?-update, then hit A while the
update was running, then what?  When did the above messages show up?

Did you then manually switch to the ChangeLog buffer edit it and save it
(causing the message about saving/writing emacs/lisp/ChangeLog?).  If so
there probably isn't enough info to do much useful.  All it then says is
that cvs-cookie is not bound, because the major-mode change removed the
buffer-local setting.

> Is there anything else I can investigate now?

I'm afraid not.

> I added it, but only on Windows, so it didn't catch.  Sorry.  (Now
> added on GNU/Linux as well.)

Let's hope it catches it next time,


        Stefan