unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: spiegel@gnu.org, emacs-devel@gnu.org
Subject: Re: special-display-buffer-names and vc-diff displays wrong result
Date: Mon, 03 Oct 2005 01:09:31 -0400	[thread overview]
Message-ID: <E1EMIZv-0005fm-0s@fencepost.gnu.org> (raw)
In-Reply-To: <20051002055458.1473025A144@gaia.local> (message from Harald Maier on Sun, 2 Oct 2005 07:54:58 +0200 (CEST))

    I am using `special-display-buffer-names' for the *vc-diff* buffer.
    If the special-display-buffer frame does not exist then the *vc-diff*
    buffer reports sometimes "No differences found.". This seems to due
    the fact that the 'vc-diff-internal' function has not written yet any
    bytes into the *vc-diff* buffer.

How would the fact that the buffer is empty have such an effect?
Can you work out the chain of events?

     The strange part is that this only
    happens if the background process ends up very fast. For example a
    diff with the cvs.gnu.org server finishes always successfully, but a
    diff with the local cvs server fails.

    I don't know how to fix this. As a workaround I put after the
    vc-diff-internal function a (sit-for 1) statement. Then it seems to
    work.

If you can deduce how this change has the effect of preventing the
problem, then we would understand the problem, and then we could look
for the right fix.

       reply	other threads:[~2005-10-03  5:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051002055458.1473025A144@gaia.local>
2005-10-03  5:09 ` Richard M. Stallman [this message]
2005-10-03 14:45   ` special-display-buffer-names and vc-diff displays wrong result Stefan Monnier
2005-10-03 19:33     ` Richard M. Stallman
2005-10-03 20:43       ` Stefan Monnier
2005-10-04 18:50         ` Richard M. Stallman
2005-10-05  3:52   ` Harald Maier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1EMIZv-0005fm-0s@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=spiegel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).