You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2018. It is now read-only.
When I use "C-c v v" to check in, vc-clearcase used to populate the comment buffer with the checkout comment.
With Emacs 24.5, this comment is being erased and replaced by "Summary: ".
I have traced the behavior. First, the code in vc-clearcase-log-edit-mode runs and inserts the comment correctly (hooray!). But then, vc-log-edit invokes log-edit with the "setup" argument set to t. log-edit reacts by running (erase-buffer) followed by (run-hooks 'log-edit-hook).
I do not understand the logic that vc-log-edit uses to decide when the "setup" argument should be true, so I gave up and added this to my .emacs file:
(defun patlhack ()
;;; body of vc-clearcase-log-edit-mode here
)
(setq log-edit-hook 'patlhack)
Yes this is a huge hack, but it does appear to work around the problem.
I have no idea how to fix this "correctly".
The text was updated successfully, but these errors were encountered:
When I use "C-c v v" to check in, vc-clearcase used to populate the comment buffer with the checkout comment.
With Emacs 24.5, this comment is being erased and replaced by "Summary: ".
I have traced the behavior. First, the code in vc-clearcase-log-edit-mode runs and inserts the comment correctly (hooray!). But then, vc-log-edit invokes log-edit with the "setup" argument set to t. log-edit reacts by running (erase-buffer) followed by (run-hooks 'log-edit-hook).
I do not understand the logic that vc-log-edit uses to decide when the "setup" argument should be true, so I gave up and added this to my .emacs file:
(defun patlhack ()
;;; body of vc-clearcase-log-edit-mode here
)
(setq log-edit-hook 'patlhack)
Yes this is a huge hack, but it does appear to work around the problem.
I have no idea how to fix this "correctly".
The text was updated successfully, but these errors were encountered: