From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: special-display-buffer-names and vc-diff displays wrong result Date: Mon, 03 Oct 2005 10:45:40 -0400 Message-ID: References: <20051002055458.1473025A144@gaia.local> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1128351558 23619 80.91.229.2 (3 Oct 2005 14:59:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 3 Oct 2005 14:59:18 +0000 (UTC) Cc: Harald Maier , spiegel@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 03 16:59:11 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EMRjh-0001GK-LT for ged-emacs-devel@m.gmane.org; Mon, 03 Oct 2005 16:56:13 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EMRjh-0002Lr-5E for ged-emacs-devel@m.gmane.org; Mon, 03 Oct 2005 10:56:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EMRif-00027z-GP for emacs-devel@gnu.org; Mon, 03 Oct 2005 10:55:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EMRia-00026E-PZ for emacs-devel@gnu.org; Mon, 03 Oct 2005 10:55:06 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EMRhW-0001MP-C3 for emacs-devel@gnu.org; Mon, 03 Oct 2005 10:53:58 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EMRZd-0005yC-Sd; Mon, 03 Oct 2005 10:45:50 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 11CCC2CF61A; Mon, 3 Oct 2005 10:45:46 -0400 (EDT) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 93C284AC010; Mon, 3 Oct 2005 10:45:40 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 8511BE6C1A; Mon, 3 Oct 2005 10:45:40 -0400 (EDT) Original-To: rms@gnu.org In-Reply-To: (Richard M. Stallman's message of "Mon, 03 Oct 2005 01:09:31 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.847, requis 5, autolearn=not spam, AWL 0.05, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:43492 Archived-At: > 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? To figure out whether there's been diffs or not, the sentinel function checks whether the resulting buffer is empty. > 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. Given his description of the problem, my guess is that somehow the sentinel is run before all the process's output has been processed. Stefan