[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Automatic updating (of display?) of the buffer *cvs* fails

From: Kim F. Storm
Subject: Automatic updating (of display?) of the buffer *cvs* fails
Date: 11 Oct 2003 01:46:35 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50

Marcus Rost and others have reported that *cvs* buffer fails to update
correctly when cvs process terminates ...

I have seen this myself occasionally (when I'm not hacking on emacs
itself - and when it happens, I already did the updates, so there's no
way to repeat it, sigh!).  But so far, I have never managed to find a
way to provoke this error at all when I've actually tried to track it

When it has happened to me, it was quite clear that emacs thought that
the display had been updated (at least to some extent) which could be
seen by moving the cursor -- it jumped in seemingly strange ways
because the buffer positions and window positions were not in sync.

Since C-l fixes it, it seems that the buffer contents have been
updated correctly by the sentinel, but it somehow forgot to redisplay
the *cvs* window (process output from the cvs program goes into
another buffer, and it is the sentinel which updates the *cvs* buffer
when the cvs program terminates).

Can any of you think of where this glitch is happening?

Since the sentinel is using insert, I would expect MODIFF to
be updated ... so who forgets to look at it?

> From: address@hidden (Kim F. Storm)
> Date: 20 Aug 2003 14:01:10 +0200
> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50
> Hi Markus,
> Is the following problem still present in CVS emacs?

> Date: Wed, 20 Aug 2003 17:18:42 -0400 (EDT)
> From: Markus Rost <address@hidden>
> Yes, it is still present, with a new bootstrapped version of today.  I
> don't understand why other people did not report this as well.  I see
> it on Emacs built on Solaris and GNU/Linux, running under X on a Sun
> (I don't have another terminal available, I can only login to a
> gnu-linux machine via ssh.).  Stefan said that he sees this problem
> occasionally, but I see it with EVERY run of cvs update.

Markus Rost <address@hidden> writes:

>        I don't know how to provide more details than I did already, except
>        for the fact that I am running emacs on X on Solaris and GNU/Linux.
>    Can you please tell me exactly what to type, starting with `emacs -q'?
>    My Emacs checkout is in ~/emacs.
> I'll try.
> This is for the current CVS emacs on X on Solaris and GNU/Linux.  Here
> are the results of C-u M-x emacs-version :
> GNU Emacs (sparc-sun-solaris2.9, X toolkit) of 2003-06-27 on hampton
> GNU Emacs (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 
> 2003-06-28 on euler
> The problem is not present with emacs -nw.
> Start Emacs with emacs -q
> Type
> M-x cvs-examine ~/emacs RET  (where ~/emacs is the Emacs checkout directory)
> Move point up to a line with a "Need-Update" file info, like
>               Need-Update             lisp/ChangeLog
> (Hopefully there is such a line when you test this.)
> Hit key "O" (cvs-mode-update)
> Eventually the minibuffer displays the message
> CVS process has completed in *cvs*
> However, the buffer *cvs* is not visibly updated.  Only after C-g or
> C-l it gets visibly updated.
> A critical function seems to be here the function cvs-sentinel.  It
> contains the following part:
>         (save-excursion (eval cvs-postproc))
>         ;; check whether something is left
>         (unless cvs-postprocess
>           ;; IIRC, we enable undo again once the process is finished
>           ;; for cases where the output was inserted in *vc-diff* or
>           ;; in a file-like buffer.  -stef
>           (buffer-enable-undo)
>           (with-current-buffer cvs-buffer
>             (cvs-update-header nil nil) ;FIXME: might need to be inline
>             (message "CVS process has completed in %s" (buffer-name)))))
> Here (eval cvs-postproc) in the first line does the updating of buffer
> *cvs*, and the message "CVS process has completed ..." comes from the
> last line.  Since I can see that message, without seeing the updated
> version of buffer *cvs*, it seems that there is a problem with the
> display engine.

Kim F. Storm <address@hidden> http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]